From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Andrew Whatson <whatson@gmail.com>
Cc: 44238@debbugs.gnu.org
Subject: bug#44238: 28.0.50; [feature/native-comp] Build trampolines for FULL_AOT builds
Date: Mon, 26 Oct 2020 13:40:48 +0000 [thread overview]
Message-ID: <xjf1rhlgl5r.fsf@sdf.org> (raw)
In-Reply-To: <CAPE069f4CRAD7L0UzOPjMR+mLebetqKOgG45JC51_GyCONuUrA@mail.gmail.com> (Andrew Whatson's message of "Mon, 26 Oct 2020 22:20:51 +1000")
Andrew Whatson <whatson@gmail.com> writes:
> Hi Andrea,
>
> In the spirit of pre-compiling as much as possible, would it make
> sense to pre-compile all the trampolines when preparing a FULL_AOT
> build?
Hi Andrew,
IMO is not worth compiling almost 1500 files for really using just a few
of them. Also the compilation is realtivelly quick (~0.2s each on my
machine), I guess the most is GCC/GAS startup time. Indeed this time is
payed only once when the primitive is redefined the first time.
That said if you want to experiment I think something like this should
do the job:
(mapatoms (λ (s)
(when (subr-primitive-p (symbol-function s))
(comp-trampoline-compile s))))
Ciao!
Andrea
next prev parent reply other threads:[~2020-10-26 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 12:20 bug#44238: 28.0.50; [feature/native-comp] Build trampolines for FULL_AOT builds Andrew Whatson
2020-10-26 13:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-11-06 20:56 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-06 22:43 ` Andrew Whatson
2020-11-06 22:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-27 17:24 ` Lars Ingebrigtsen
2021-08-29 21:23 ` Andrew Whatson
2021-08-29 21:26 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjf1rhlgl5r.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=44238@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=whatson@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.