From: Han-Wen <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: status: separation of expansion/optimization/memoization/execution
Date: Sat, 3 Aug 2002 14:12:23 +0200 [thread overview]
Message-ID: <15691.51367.455100.152498@blauw.xs4all.nl> (raw)
In-Reply-To: <Pine.GSO.4.05.10208022349150.5209-100000@sallust.ida.ing.tu-bs.de>
dirk@sallust.ida.ing.tu-bs.de writes:
> The effect so far is, that booting guile takes noticably longer (at least
> 15%), but for example executing the test-suite is almost as fast as before
How do you measure that effectively? I now installed my new-gc guile,
and starting it up takes as long as it used to (the speed up seems to
have been disappeared.) Isn't the benchmark suite a much better test?
Is there some magical command that shows the startup time? (Would be
easy to implement, just do something similar to gc-stats).
FWIW, I "installed" some of the GC benchmarks over here --pretty
trivial-- and the code is GPL, but probably not (c) assigned. We can't
accept it then, Marius (right?), so shall I try asking the guy for a
disclaimer & assignment? (I think it has a slim chance working).
BTW, on a completely different note: I realized that it should not be
difficult to maintain coverage statistics for all primitive
(implemented in C) subroutines: when they are invoked a flag is set.
Is that possible? Wouldn't that be very good for testing the
test-suite? Any thoughts?
--
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-08-03 12:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 22:42 status: separation of expansion/optimization/memoization/execution Dirk Herrmann
2002-08-02 23:15 ` Rob Browning
2002-08-02 23:47 ` Han-Wen
2002-08-02 23:20 ` Dale P. Smith
2002-08-03 12:12 ` Han-Wen [this message]
2002-08-04 1:51 ` Dirk Herrmann
2002-08-04 2:03 ` Han-Wen
2002-08-04 2:05 ` Tom Lord
2002-08-04 2:11 ` Tom Lord
2002-08-04 2:20 ` for example Tom Lord
2002-08-04 2:27 ` i know -- let's play bridge! Tom Lord
2002-08-04 2:46 ` Tom Lord
2002-08-04 2:50 ` Thomas Bushnell, BSG
2002-08-04 2:57 ` Tom Lord
2002-08-04 3:04 ` Thomas Bushnell, BSG
2002-08-04 3:43 ` Tom Lord
2002-08-04 3:53 ` Thomas Bushnell, BSG
2002-08-04 4:03 ` Tom Lord
2002-08-04 4:10 ` Tom Lord
2002-08-04 3:50 ` Tom Lord
2002-08-04 3:55 ` Tom Lord
2002-08-04 3:58 ` Tom Lord
2002-08-05 18:15 ` status: separation of expansion/optimization/memoization/execution Marius Vollmer
2002-08-05 18:11 ` Marius Vollmer
2002-08-07 20:51 ` Dirk Herrmann
2002-08-10 13:01 ` Marius Vollmer
2002-08-14 19:30 ` Dirk Herrmann
2002-08-26 22:11 ` Marius Vollmer
2002-08-05 18:36 ` Neil Jerram
2002-08-07 20:55 ` Dirk Herrmann
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=15691.51367.455100.152498@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--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).