From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: marking overhead, and on the cost of conditionals in hot code
Date: Sat, 17 Jan 2009 23:37:22 +0100 [thread overview]
Message-ID: <87ocy5v9st.fsf@gnu.org> (raw)
In-Reply-To: 49dd78620901171048n1946754bm5cae2085610604f1@mail.gmail.com
"Neil Jerram" <neiljerram@googlemail.com> writes:
> It seems like a lot of things are starting to depend on whether or not
> we move to BDW-GC. (This, the fix I just did for NetBSD,
> scm_init_guile, forthcoming work on threads and mutex locking
> inconsistencies, ...) We should aim to reach a definitive decision on
> this soon!
Right. Here's my (small) roadmap:
1. Experiment a bit more with static allocation, notably for subrs,
and see whether it's worth it.
2. Provide additional benchmarking results, based on those by Clinger,
Hansen et al., which are in the repo. I'd like to have a
reasonable understanding of what they do, though.
Additional feedback from interested parties could also be helpful in
trying to reach a decision.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-01-17 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 22:00 marking overhead, and on the cost of conditionals in hot code Andy Wingo
2009-01-17 18:48 ` Neil Jerram
2009-01-17 22:37 ` Ludovic Courtès [this message]
2009-01-17 22:30 ` Ludovic Courtès
2009-01-19 3:35 ` Han-Wen Nienhuys
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=87ocy5v9st.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).