From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: vm status update
Date: Sun, 11 Jan 2009 18:35:19 +0100 [thread overview]
Message-ID: <m3tz85n3u0.fsf@pobox.com> (raw)
Hey hackers,
I just finished up a lot of typing at the manual, and I hope I'm done
with that. The net result is that the VM is documented quite thoroughly,
and the compiler as well. I'll send those documents to the list in
separate mails for inline comments.
Otherwise, in the course of documentation, I've made a few minor
cleanups, some internal name changes and such. No sense polishing a
turd, they say.
I had an idea regarding unit tests recently: since GHIL and GLIL now
have (documented!) S-expression representations, we should be able to
easily and expressively test individual compiler passes. Looking forward
to that.
I also had another realization, that now that VM frames go into stack
structures, that statprof should work with the VM. Have yet to check
though.
Anyway, just some babblings. I'll probably switch to benchmarking and
profiling sometime soon. I also need to merge in master to vm, it's been
a while and there are probably some conflicts.
So that's my status. Happy hacking!
Andy
--
http://wingolog.org/
next reply other threads:[~2009-01-11 17:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 17:35 Andy Wingo [this message]
2009-01-13 8:05 ` vm status update 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
2008-12-26 17:24 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
2009-01-06 9:52 ` Andy Wingo
2009-01-06 14:54 ` 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=m3tz85n3u0.fsf@pobox.com \
--to=wingo@pobox.com \
--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).