From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: guile performance - Ackermann function: way slower than emacs, slower still if compiled
Date: Thu, 13 Aug 2009 00:28:35 +0200 [thread overview]
Message-ID: <m3hbwcll9o.fsf@pobox.com> (raw)
In-Reply-To: <87ab2aotw1.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 08 Aug 2009 23:52:46 +0200")
Heya,
On Sat 08 Aug 2009 23:52, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> Perhaps the deal is that 1+ is not being inlined. It seems to be calling
>> out to the 1+ procedure, which is a primitive, actually making it a
>> bit slower. I'll see what I can do.
>
> Currently, invoking subrs conses, which is Bad(TM).
Indeed.
> Code that keeps invoking `1+' and `1-' must suffer from this.
Not any more! There are add1 and sub1 instructions now.
A
--
http://wingolog.org/
next prev parent reply other threads:[~2009-08-12 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 9:28 guile performance - Ackermann function: way slower than emacs, slower still if compiled Ken Raeburn
2009-08-04 13:52 ` Marijn Schouten (hkBst)
2009-08-04 15:56 ` Ken Raeburn
2009-08-05 9:06 ` Andy Wingo
2009-08-05 14:06 ` Ken Raeburn
2009-08-06 7:31 ` Ken Raeburn
2009-08-26 22:39 ` Neil Jerram
2009-08-06 16:30 ` entering and leaving guile mode, and GC stack protection (was Re: guile performance - Ackermann function: way slower than emacs, slower still if compiled) Ken Raeburn
2009-08-12 22:06 ` entering and leaving guile mode, and GC stack protection Andy Wingo
2009-08-14 7:58 ` Ludovic Courtès
2009-08-08 21:52 ` guile performance - Ackermann function: way slower than emacs, slower still if compiled Ludovic Courtès
2009-08-12 22:28 ` Andy Wingo [this message]
2009-08-05 10:42 ` Andy Wingo
2009-08-06 15:59 ` Andy Wingo
2009-08-07 17:27 ` Andy Wingo
2009-08-05 11:15 ` Andy Wingo
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=m3hbwcll9o.fsf@pobox.com \
--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).