From: tomas@tuxteam.de
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] use tail pointer for LOOP
Date: Thu, 17 Jun 2010 07:10:21 +0200 [thread overview]
Message-ID: <20100617051021.GA26623@tomas> (raw)
In-Reply-To: <87fx0msv9z.fsf@lola.goethe.zz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Jun 16, 2010 at 08:10:48PM +0200, David Kastrup wrote:
> tomas@tuxteam.de writes:
[...]
> > This has intrigued me for quite a while.
> > (Maybe the tail pointer version could be done more elegantly: I'd be
> > delighted to be taught more :)
[...]
> Did you byte-compile?
Thanks, David. Good point. That's the outcome:
Without byte compilation:
Reverse: (2.165832 5 0.7267649999999994)
Tail pointer: (2.795332 4 0.8909630000000011)
Byte compiling copy1, copy2 (and runtwo, for good measure, but I
wouldn't expect that to matter):
Reverse: (1.006534 3 0.682734)
Tail pointer: (1.305476 4 0.9159619999999986)
Still, reversing seems to be worth it (by some 30 percent). Unless we
find some way to streamline the tail pointer better.
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFMGa49Bcgs9XrR2kYRAu/DAJwK+aD1fiV3nISL212UR8JqFTaokwCdEt/G
D64HURkJwg2EduxzFNvfY9g=
=wSpa
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-06-17 5:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 21:56 O(N^2) behavior in LOOP Daniel Colascione
2010-05-29 22:06 ` Daniel Colascione
2010-05-29 22:14 ` Lennart Borgman
2010-05-29 22:35 ` Geoff Gole
2010-05-29 23:58 ` [PATCH] use tail pointer for LOOP (Was: Re: O(N^2) behavior in LOOP) Daniel Colascione
2010-05-30 0:45 ` Ken Raeburn
2010-05-30 0:49 ` Daniel Colascione
2010-06-16 17:44 ` tomas
2010-06-16 18:10 ` [PATCH] use tail pointer for LOOP David Kastrup
2010-06-17 5:10 ` tomas [this message]
2010-06-17 7:18 ` Thien-Thi Nguyen
2010-06-17 9:22 ` tomas
2010-06-17 10:03 ` Thien-Thi Nguyen
2010-06-17 14:05 ` tomas
2010-06-17 15:16 ` Thien-Thi Nguyen
2010-06-17 10:12 ` Thien-Thi Nguyen
2010-06-17 20:48 ` Stefan Monnier
2010-06-18 7:07 ` David Kastrup
2010-06-18 13:40 ` Stefan Monnier
2010-05-30 17:05 ` Štěpán Němec
2010-05-30 17:09 ` Daniel Colascione
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100617051021.GA26623@tomas \
--to=tomas@tuxteam.de \
--cc=dak@gnu.org \
--cc=emacs-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).