From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: vm status update
Date: Mon, 05 Jan 2009 22:03:24 +0100 [thread overview]
Message-ID: <87d4f1ea8z.fsf@gnu.org> (raw)
In-Reply-To: m3tz8dr5zg.fsf@pobox.com
Hello,
Andy Wingo <wingo@pobox.com> writes:
> Well, there are larger tests, in that the normal test suite passes with
> VM-compiled code (e.g. ice-9 and all that).
Yes, I remember reading that (and that is reassuring!), but I think it's
good to have unit tests for the compiler/VM too.
> And there are smaller tests, which test that VM compilation and
> execution produces the same result as interpretation. But there are no
> unit tests of the compiler itself. Also, these particular tests are not
> yet integrated with the main test suite.
I see.
> Benchmark-wise, there's not much. I am not currently running many
> benchmarks, fwiw -- been focusing more on correctness.
Maybe "we" could start focusing on that now that the VM/compiler have
matured a lot?
Thanks!
Ludo'.
next prev parent reply other threads:[~2009-01-05 21:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 17:24 vm status update Andy Wingo
2008-12-28 22:50 ` Neil Jerram
2009-01-05 16:06 ` Ludovic Courtès
2009-01-05 16:45 ` Neil Jerram
2009-01-05 19:53 ` Ludovic Courtès
2009-01-05 17:57 ` Andy Wingo
2009-01-05 21:03 ` Ludovic Courtès [this message]
2009-01-06 9:52 ` Andy Wingo
2009-01-06 14:54 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2009-03-06 19:52 Andy Wingo
2009-03-06 22:31 ` Ludovic Courtès
2009-03-08 22:40 ` Neil Jerram
2009-03-10 21:04 ` Andy Wingo
2009-02-14 22:32 Andy Wingo
2009-02-16 11:47 ` Marijn Schouten (hkBst)
2009-03-08 11:49 ` Neil Jerram
2009-03-10 21:36 ` Andy Wingo
2009-03-12 20:49 ` Neil Jerram
2009-01-11 17:35 Andy Wingo
2009-01-13 8:05 ` Ludovic Courtès
2008-09-13 15:59 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=87d4f1ea8z.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).