From: Andy Wingo <wingo@pobox.com>
To: Michael Ellis <michael.f.ellis@gmail.com>
Cc: Guile bug <bug-guile@gnu.org>
Subject: Re: Loop optimization
Date: Tue, 08 Mar 2011 22:43:16 +0100 [thread overview]
Message-ID: <m38vwp9tl7.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTi=obFGL4ckb8giaAvhAuk4kfytpFXf79=w-0YJL@mail.gmail.com> (Michael Ellis's message of "Mon, 7 Mar 2011 18:10:33 -0500")
On Tue 08 Mar 2011 00:10, Michael Ellis <michael.f.ellis@gmail.com> writes:
> Thanks for the education, Andy, and congrats again on the guile
> compiler implementation. Your version handily outperforms the fastest
> python implementation I know.
Thanks, but there is still a ways to go. If guile can count to 10
million in half a second, that means it's spending 100+ cycles per loop,
when it could be spending 5 or something. I figure we have a good
factor of 4 to squeeze out easily with native compilation, and more with
flow analysis and untagging and such.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-03-08 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 21:01 Loop optimization Michael Ellis
2011-03-07 21:36 ` Andy Wingo
2011-03-07 23:10 ` Michael Ellis
2011-03-08 0:28 ` Mark H Weaver
2011-03-08 0:30 ` Mark H Weaver
2011-03-08 21:43 ` 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=m38vwp9tl7.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=michael.f.ellis@gmail.com \
/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).