From: "Mattias Engdegård" <mattiase@acm.org>
To: 53482@debbugs.gnu.org
Subject: bug#53482: Byte-code speedup [PATCH]
Date: Sun, 23 Jan 2022 17:57:09 +0100 [thread overview]
Message-ID: <BBCA676A-1875-4F0F-9527-52ACF2CF7CBA@acm.org> (raw)
The branch scratch/bytecode-speedup now contains a set of related improvements to speed up the byte-code interpreter. If someone is allergic to Git, I could post them as separate patches.
Performance is improved in many ways but is mostly focussed on making Elisp's lamentably slow function calls faster, which should benefit a lot of code. Operations on fixnums have also been sped up, as well as some data structure access.
Equally importantly, the C stack requirements has shrunk meaning that users can recurse deeper before getting a segfault. For example, bytecode is no longer copied to a stack buffer for execution. I intend to carry this process further in a set of follow-up patches, but the current changes are definitely good enough on their own.
I have run a wide set of benchmarks; regressions are rare but obviously not all code benefits equally. Most code becomes at least a little faster.
Unless there are good arguments not to, I'll merge it to master shortly.
next reply other threads:[~2022-01-23 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 16:57 Mattias Engdegård [this message]
2022-01-23 18:33 ` bug#53482: Byte-code speedup [PATCH] Lars Ingebrigtsen
2022-01-23 21:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 21:30 ` Lars Ingebrigtsen
2022-01-24 15:47 ` Mattias Engdegård
2022-01-23 22:20 ` Dmitry Gutov
2022-01-23 22:44 ` Dmitry Gutov
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=BBCA676A-1875-4F0F-9527-52ACF2CF7CBA@acm.org \
--to=mattiase@acm.org \
--cc=53482@debbugs.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).