From: ludo@gnu.org (Ludovic Courtès)
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: summer of code ideas
Date: Mon, 07 Mar 2011 23:27:04 +0100 [thread overview]
Message-ID: <87d3m2va6f.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTi=YBX_p490jP6zCWgJDFftCDxbS2zNVF5ZDfOva@mail.gmail.com> (Noah Lavine's message of "Mon, 7 Mar 2011 17:11:14 -0500")
Hi!
Noah Lavine <noah.b.lavine@gmail.com> writes:
> Yes, it's been a while since we talked about that :-). I still want to
> do it, though. The current status as I see it is that I have a
> prototype JIT that works, and a plausible way to integrate it into
> Guile's VM. What needs to happen now is to write all of the opcodes as
> JIT functions (the prototype had five or so opcodes). Since writing
> them by hand would cause an absurd amount of code duplication, I
> wanted to do it automatically.
Yes.
> We talked about having a Scheme-based language that could compile to
> both plain C and JIT, but decided that would make the VM too
> complicated,
Maybe I forgot to feed that thread, but I think it might be easier to
have a high-level representation the VM opcodes as sexps (possibly a
subset of Scheme), and then write the C files from that.
Though the main difficulty is to find a sufficiently expressive way to
write opcodes in.
> I notice that GCC now has the ability to use plugins,
The plug-in API doesn’t allow plug-ins to add new front-ends
(info "(gccint) Plugins").
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-03-07 22:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 19:51 summer of code ideas Andy Wingo
2011-03-07 20:12 ` Noah Lavine
2011-03-07 21:33 ` Ludovic Courtès
2011-03-07 22:11 ` Noah Lavine
2011-03-07 22:27 ` Ludovic Courtès [this message]
2011-03-07 22:37 ` Noah Lavine
2011-03-08 13:00 ` Ludovic Courtès
2011-03-07 20:13 ` CPAN for Guile Andreas Rottmann
2011-03-07 21:12 ` Andy Wingo
2011-03-28 23:03 ` Andreas Rottmann
2011-03-07 20:40 ` summer of code ideas Noah Lavine
2011-03-07 20:46 ` Andy Wingo
2011-03-07 21:27 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2011-03-07 20:23 Mike Gran
2011-03-07 21:25 ` Jose A. Ortega Ruiz
2011-03-08 1:10 ` Mark H Weaver
2011-03-08 1:45 Mike Gran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3m2va6f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).