From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: A big hole where the evaluator used to be...
Date: Fri, 11 Dec 2009 20:18:31 +0100 [thread overview]
Message-ID: <m3ljh9b9q0.fsf@pobox.com> (raw)
In-Reply-To: <87iqcdlaj9.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 11 Dec 2009 16:50:50 +0000")
On Fri 11 Dec 2009 17:50, Neil Jerram <neil@ossau.uklinux.net> writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> Thanks! I finally had time to write up some of this here:
>>
>> http://wingolog.org/archives/2009/12/09/in-which-our-protagonist-forgoes-modesty
>
> Nice. But I didn't understand where you said that all the unit tests go
> through the evaluator. Apart from those that use eval explicitly, don't
> they all just get compiled and VM'd?
They don't, actually. They are all run with the evaluator. See
609edba7eaa2bb30df90a09541a48d97ab4a3bf8. We should probably enable it
again now.
>> Another side of this is compile-time speed; psyntax-pp.scm takes forever
>> to compile now, like 4 or 8 minutes.
>
> And much longer than that (~30 mins?) on my ancient P3 laptop! (But
> it's still worth it!)
Uf, 30 minutes. Way too long, eh. I agree it's worth it but that we need
to profile things and see what improvements we can get. Also, we could
focus on compiler improvements that would help the evaluator -- computed
goto might be a good one, so that our memoized-expression-case could
compile to something that looks more like the compilation of `case'.
Peace,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-12-11 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 19:08 A big hole where the evaluator used to be Neil Jerram
2009-12-11 10:27 ` Andy Wingo
2009-12-11 16:50 ` Neil Jerram
2009-12-11 19:18 ` Andy Wingo [this message]
2009-12-11 22:56 ` Ludovic Courtès
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=m3ljh9b9q0.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).