From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Why bother porting Guile to BDW-GC?
Date: Wed, 12 Nov 2008 09:28:49 +0100 [thread overview]
Message-ID: <87d4h1qrem.fsf@gnu.org> (raw)
In-Reply-To: m3od0matrh.fsf@pobox.com
Hi,
Andy Wingo <wingo@pobox.com> writes:
> Some benchmarking would be really nice ;-)
>
> Like these for example:
>
> http://www.ccs.neu.edu/home/will/Twobit/benchmarksAbout.html
Yes, see, e.g.,
http://thread.gmane.org/gmane.lisp.guile.devel/7803
http://thread.gmane.org/gmane.lisp.guile.devel/7803/focus=7810
The GC benchmarks used by Lars Hansen in his PhD and referred to in the
above message are already in the Git tree. I'll report about them ASAP.
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-11-12 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 15:58 Why bother porting Guile to BDW-GC? Ludovic Courtès
2008-11-09 2:23 ` Han-Wen Nienhuys
2008-11-09 2:27 ` Han-Wen Nienhuys
2008-11-09 18:25 ` Ludovic Courtès
2008-11-10 20:57 ` Neil Jerram
2008-11-11 20:11 ` Ludovic Courtès
2008-11-11 20:32 ` Andy Wingo
2008-11-12 8:28 ` Ludovic Courtès [this message]
2008-11-10 21:10 ` Ludovic Courtès
2008-11-11 20:42 ` 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=87d4h1qrem.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).