unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: SRFI-1 in Scheme
Date: Wed, 14 Jul 2010 00:27:53 +0200	[thread overview]
Message-ID: <m3tyo381au.fsf@unquote.localdomain> (raw)
In-Reply-To: <87hbk3uj8c.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 14 Jul 2010 00:09:39 +0200")

Greets

On Wed 14 Jul 2010 00:09, ludo@gnu.org (Ludovic Courtès) writes:

> Just to make sure, did you read the figures right?  With the debug
> engine, the slowdown is noticeable.

Yes, I saw the numbers :)

> 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.

Tracing and call-counting profiling too. They will be used when stepping soon.

>> At the very least, one should be able to switch VMs.
>
> You mean switch VMs for the code being executed?

Yes.

>  (For code to be
> executed than can already be done using ‘vm-apply’.)

That would only apply until a function was subsequently called from C.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-07-13 22:27 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
2010-07-13 22:27     ` Andy Wingo [this message]
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=m3tyo381au.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).