From: Dan Nicolaescu <dann@ics.uci.edu>
To: tromey@redhat.com
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: indirect threading for bytecode interpreter
Date: Fri, 18 Sep 2009 12:15:41 -0700 (PDT) [thread overview]
Message-ID: <200909181915.n8IJFfw7006915@godzilla.ics.uci.edu> (raw)
In-Reply-To: <m3ab0tldsb.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 17 Sep 2009 10:46:44 -0600")
Tom Tromey <tromey@redhat.com> writes:
> This patch implements indirect threading for the Emacs bytecode
> interpreter. It uses a GNU C extension, and falls back to the current
> switch-based code if Emacs is compiled with some other compiler.
>
> This speeds up the bytecode interpreter a bit. On my benchmark, it
> improved the overall time between 4-7% (lots of noise in the runs).
> That isn't bad when you consider that Fbyte_code was the 3rd biggest
> time user (the first two being re_match_2_internal and mark_object).
If your patch applies to emacs-22.3 (quite likely), and you are curious,
you might want to test the performance there. The overhead of
mark_object should be lower in that version (it's higher in 23 because
of the way charsets are represented).
next prev parent reply other threads:[~2009-09-18 19:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 16:46 indirect threading for bytecode interpreter Tom Tromey
2009-09-17 18:21 ` Stefan Monnier
2009-09-17 19:20 ` Helmut Eller
2009-09-17 19:38 ` Tom Tromey
2009-09-17 20:41 ` Helmut Eller
2009-09-17 21:06 ` Tom Tromey
2009-09-17 22:48 ` Helmut Eller
2009-09-18 0:59 ` Stefan Monnier
2009-09-18 2:59 ` Tom Tromey
2009-09-17 20:43 ` Stefan Monnier
2009-09-17 20:57 ` Tom Tromey
2009-09-18 19:15 ` Dan Nicolaescu [this message]
2009-09-18 20:26 ` Tom Tromey
2009-09-21 1:58 ` Dan Nicolaescu
2009-09-21 3:17 ` Tom Tromey
2009-09-21 13:13 ` Stefan Monnier
2009-09-21 13:21 ` David Kastrup
2009-09-21 13:47 ` joakim
2009-09-21 14:46 ` Stefan Monnier
2009-09-21 14:27 ` Tom Tromey
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=200909181915.n8IJFfw7006915@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=tromey@redhat.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.
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).