From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: master 289000e: Merge branch 'feature/native-comp' into trunk
Date: Mon, 26 Apr 2021 17:33:30 +0200 [thread overview]
Message-ID: <87eeexm56d.fsf@telefonica.net> (raw)
In-Reply-To: YIbUE9tdMkOYcvSQ@ACM
Alan Mackenzie <acm@muc.de> writes:
> I must be doing something differently from these people, but I can't
> identify what. Native compilation just doesn't seem to be working for
> me, yet. How much of a speed up should it give me? Surely more than 5%
> - 10%?
native-comp speeds up Elisp, and even then there are lots of cases where
the change is hardly noticeable.
Let's say your code spends 90% on the C core and 10% on Elisp. If
native-comp brings a 2x speed up, you'll only observe about 5%
improvement.
C code is opaque to native-comp and puts a hard limit on how much it can
optimize Elisp. Thus I hope that in the future more and more code will
be moved from C to Elisp. And other areas can benefit too: one thing
which IMO has lots of potential is to native-compile regexps.
next prev parent reply other threads:[~2021-04-26 15:33 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210425182503.25223.81072@vcs0.savannah.gnu.org>
[not found] ` <20210425182508.6CC7C2094D@vcs0.savannah.gnu.org>
2021-04-25 18:36 ` master 289000e: Merge branch 'feature/native-comp' into trunk Andrea Corallo via Emacs development discussions.
2021-04-25 18:40 ` Eli Zaretskii
2021-04-25 18:59 ` Andrea Corallo via Emacs development discussions.
2021-04-25 20:25 ` Eli Zaretskii
2021-04-25 18:45 ` Óscar Fuentes
2021-04-25 20:03 ` Alan Mackenzie
2021-04-25 20:14 ` Eli Zaretskii
2021-04-25 21:55 ` Alan Mackenzie
2021-04-26 11:40 ` Eli Zaretskii
2021-04-26 13:21 ` Alan Mackenzie
2021-04-26 13:45 ` Eli Zaretskii
2021-04-26 14:54 ` Alan Mackenzie
2021-04-26 15:12 ` Eli Zaretskii
2021-04-26 17:02 ` Alan Mackenzie
2021-04-26 17:13 ` Stefan Monnier
2021-04-26 17:25 ` Eli Zaretskii
2021-04-28 11:34 ` Alan Mackenzie
2021-04-28 12:26 ` Eli Zaretskii
2021-04-28 12:32 ` Alan Mackenzie
2021-04-28 13:01 ` Eli Zaretskii
2021-04-28 19:09 ` Andrea Corallo via Emacs development discussions.
2021-04-26 15:33 ` Óscar Fuentes [this message]
2021-04-26 15:58 ` Eli Zaretskii
2021-04-26 16:30 ` Óscar Fuentes
2021-04-26 17:11 ` Alan Mackenzie
2021-04-26 20:02 ` Óscar Fuentes
2021-04-28 14:07 ` Alan Mackenzie
2021-04-28 15:10 ` Óscar Fuentes
2021-04-26 15:37 ` Stefan Monnier
2021-04-26 16:06 ` Andrea Corallo via Emacs development discussions.
2021-04-26 17:05 ` Alan Mackenzie
2021-04-25 21:48 ` Stefan Monnier
2021-04-25 22:41 ` Stefan Kangas
2021-04-25 22:57 ` Clément Pit-Claudel
2021-04-26 16:16 ` Andrea Corallo via Emacs development discussions.
2021-04-26 13:03 ` wilde
2021-04-26 13:18 ` Minimal recommended version of gcc/libgccjit for native-comp (was: master 289000e: Merge branch 'feature/native-comp' into trunk) wilde
2021-04-26 15:58 ` Minimal recommended version of gcc/libgccjit for native-comp Stefan Monnier
2021-04-26 16:16 ` Eli Zaretskii
2021-04-26 16:32 ` Andrea Corallo via Emacs development discussions.
2021-04-26 16:54 ` Eli Zaretskii
2021-04-26 20:53 ` Andrea Corallo via Emacs development discussions.
2021-04-27 3:52 ` Richard Stallman
2021-04-26 16:18 ` Andrea Corallo via Emacs development discussions.
2021-04-26 16:12 ` Andrea Corallo via Emacs development discussions.
2021-04-27 14:21 ` wilde
2021-04-27 16:35 ` Andrea Corallo via Emacs development discussions.
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=87eeexm56d.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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).