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: further guile-vm integration
Date: Sat, 23 Aug 2008 11:12:44 -0700	[thread overview]
Message-ID: <m33akvtxb7.fsf@pobox.com> (raw)
In-Reply-To: <87hc9cam62.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 22 Aug 2008 21:23:49 +0200")

Hi,

On Fri 22 Aug 2008 12:23, ludo@gnu.org (Ludovic Courtès) writes:

> Besides, do you have an automatic compilation approach in mind (à la
> Python) or something explicit, possibly with source/binary time-stamp
> comparison?

I don't know really. Currently it's explicit. But automatic could be
interesting; you have to check timestamps anyway to see if the compiled
file is actually older than the source file, in which case you want to
warn and load the source file instead. But in general I would follow
emacs' lead in this regard.

> Did you benchmark the thing?  I remember speed improvements were not all
> that clear back when I played with Guile-VM.

I've been benchmarking, yes, and the advantages are now pretty clear, at
runtime, and the startup advantages are excellent. But I have yet to
compile boot-9.scm.

> Besides, before making a release, it may be worth thinking about
> potential GO format changes that we'd possibly want to make in the
> future.

Sure, definitely.

> One big thing I had in mind was the use of word-aligned
> bytecodes, which should improve performance on several architectures

Sure, would be a great thing to try.

Andy
-- 
http://wingolog.org/




      reply	other threads:[~2008-08-23 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 20:50 further guile-vm integration Andy Wingo
2008-08-22  2:30 ` Han-Wen Nienhuys
2008-08-22  7:43   ` Ludovic Courtès
2008-08-22 19:23 ` Ludovic Courtès
2008-08-23 18:12   ` Andy Wingo [this message]

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=m33akvtxb7.fsf@pobox.com \
    --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).