From: Doug Evans <dje@sebabeach.org>
To: cgen@sourceware.org
Subject: guile 1.9.2
Date: Sun, 30 Aug 2009 20:49:00 -0000 [thread overview]
Message-ID: <20090830204909.AE79F6E3D5@sebabeach.org> (raw)
Guile 1.9.2 has a faster engine (based on some simple, and admittedly
too-trivial experiments), but there is hope.
I tried running cgen with it and after getting some issues out of the way (*1),
I ran into some problems that seemed internal to Guile so I'm punting for now.
mzscheme and qscheme are faster.
qscheme is simple yet fast, although gcc-specific.
I'm guessing it's also a bit incomplete for what we need, but that can change.
mzscheme is the fastest I've tried.
Some might like to develop cgen in drscheme.
Ports to any of these might be interesting.
Removing COS along the way wouldn't be a bad idea. In time.
[Insert plans for what I'd *really* like to see happen:
a Scheme that used cgen to generate parts of its dynamic compilation backend.]
(*1) Guile 1.9.2 doesn't like top level definitions inside conditionals,
for example. That may change (or may just be temporary) of course.
reply other threads:[~2009-08-30 20:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090830204909.AE79F6E3D5@sebabeach.org \
--to=dje@sebabeach.org \
--cc=cgen@sourceware.org \
/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).