From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.1-33-ga2a6c0e
Date: Sun, 08 May 2011 01:30:01 +0200 [thread overview]
Message-ID: <m3pqnu6qdi.fsf@unquote.localdomain> (raw)
In-Reply-To: <87tyd6gyc5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 07 May 2011 20:27:54 +0200")
On Sat 07 May 2011 20:27, ludo@gnu.org (Ludovic Courtès) writes:
>> * libguile/vm-engine.c (vm_engine): Cache the scm_i_thread* instead of
>> the dynstate, so we can use the thread for ticks.
>
> What effect does it have on performance? Registers are scarce on x86...
I did this because there were several million __tls_getaddr calls when
compiling psyntax.scm, which presumably are more expensive than either a
cached memory ref or a register. In any case it's not more local vars
than before...
But that's not your question. Answer: I'm pretty sure it's an
improvement, but it would be good to see numbers :)
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-05-07 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1QI6rh-0003ck-EO@vcs-noshell.in.savannah.gnu.org>
2011-05-07 18:27 ` [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.1-33-ga2a6c0e Ludovic Courtès
2011-05-07 23:30 ` Andy Wingo [this message]
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=m3pqnu6qdi.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).