From: Han-Wen <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org, guile-user@gnu.org
Subject: benchmarking framework
Date: Sat, 20 Jul 2002 14:46:23 +0200 [thread overview]
Message-ID: <15673.23455.874112.265246@blauw.xs4all.nl> (raw)
In-Reply-To: <Pine.GSO.4.05.10207200332430.5632-100000@sallust.ida.ing.tu-bs.de>
dirk@sallust.ida.ing.tu-bs.de writes:
> I have taken the freedom to add a benchmarking framework to guile. It is
> a simple adaptation from the testing framework. A lot of code has been
> copied from there. Well, maybe at some time it would be better to extract
> the common parts into a module.
>
> Whatever, here's a short introduction: benchmarks are placed in the
> directory benchmark-suite/benchmarks. They are ordinary scheme files, but
> with the .bm extension. At least these files are detected automatically.
> Others can also be specified explicitly.
there is a nice suite of scheme GC benchmarks in
http://www.ccs.neu.edu/home/will/GC/sourcecode.html,
however, is it required that authors of these also have disclaimers at gnu?
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-20 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 2:13 benchmarking framework Dirk Herrmann
2002-07-20 8:44 ` Neil Jerram
2002-07-21 12:03 ` Dirk Herrmann
2002-07-20 12:13 ` Marius Vollmer
2002-07-20 12:46 ` Han-Wen [this message]
2002-07-20 14:01 ` Neil Jerram
2002-07-20 19:11 ` Rob Browning
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=15673.23455.874112.265246@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).