From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: SRFI-1 in Scheme
Date: Wed, 14 Jul 2010 00:09:39 +0200 [thread overview]
Message-ID: <87hbk3uj8c.fsf@gnu.org> (raw)
In-Reply-To: m34og3axbc.fsf@unquote.localdomain
Hey!
Andy Wingo <wingo@pobox.com> writes:
> On Tue 13 Jul 2010 00:57, ludo@gnu.org (Ludovic Courtès) writes:
>
>> The attached patch is a first stab at re-implementing SRFI-1 in
>> Scheme.
>>
>> IOW, with the debug engine (currently the default) and for large lists
>> ‘fold’ in Scheme is ~9% slower than in C; for small lists it’s ~17%
>> slower.
>>
>> With the regular engine, Scheme is ~2% faster for large lists and still
>> ~5% slower for small lists.
>>
>> I’m tempted to put this in
>
> Cool, looks good to me.
Just to make sure, did you read the figures right? With the debug
engine, the slowdown is noticeable.
>> and then make the regular engine the default unless ‘--debug’ is
>> specified.
>
> I would prefer to keep the debug VM as the default.
AFAICS the only difference between the two engine is VM_USE_HOOKS.
Hooks are only used in (system vm coverage) at this point, so we don’t
lose much by disabling them.
Am I overlooking something?
> At the very least, one should be able to switch VMs.
You mean switch VMs for the code being executed? (For code to be
executed than can already be done using ‘vm-apply’.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-07-13 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 22:57 SRFI-1 in Scheme Ludovic Courtès
2010-07-13 21:25 ` Andy Wingo
2010-07-13 22:09 ` Ludovic Courtès [this message]
2010-07-13 22:27 ` Andy Wingo
2010-07-13 22:44 ` Ludovic Courtès
2010-07-14 7:41 ` Andy Wingo
2010-07-15 21:40 ` Ludovic Courtès
2010-07-19 20:30 ` Andy Wingo
2010-07-20 16:35 ` Ludovic Courtès
2010-07-20 20:11 ` Andy Wingo
2010-07-21 23:10 ` Ludovic Courtès
2010-07-20 20:15 ` Andy Wingo
2010-09-01 16:04 ` Allowing the choice of a VM engine? Ludovic Courtès
2010-09-03 5:23 ` Andy Wingo
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=87hbk3uj8c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.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).