From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58580@debbugs.gnu.org, akrl@sdf.org
Subject: bug#58580: 29.0.50; Ahead-of-time compilation for a few more files?
Date: Mon, 17 Oct 2022 21:35:31 +0200 [thread overview]
Message-ID: <875ygickfw.fsf@gnus.org> (raw)
In-Reply-To: <8335bm36kd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 17 Oct 2022 16:47:46 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> However, now we are saying that having some files precompiled is more
> convenient, as it makes the first startup of a newly built/installed
> Emacs faster and smoother. (It only affects the first startup after
> building a new version.) So the motivation is different, but I don't
> see why the same solution couldn't satisfy this one as well. After
> all, the solution is solid and tested by 2 releases.
I'm not 100% sure I understand -- by "solution" here, you mean
COMPILE_FIRST?
>> But I guess we'd have to introduce a new mechanism for this, like
>> COMPILE_ELN_EXTRA or something, if we want to AOT them anyway?
>
> Why not use the same mechanism?
Because it's slower to do eln compilation in COMPILE_FIRST -- it's
faster later, once Emacs has been built with nativecomp. So these extra
eln bits should be done around the same time as compile-main, or rather:
During compile-main, so that we get max parallelism, too.
next prev parent reply other threads:[~2022-10-17 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 9:11 bug#58580: 29.0.50; Ahead-of-time compilation for a few more files? Lars Ingebrigtsen
2022-10-17 9:28 ` Andrea Corallo
2022-10-17 10:16 ` Eli Zaretskii
2022-10-17 11:25 ` Lars Ingebrigtsen
2022-10-17 13:34 ` Eli Zaretskii
2022-10-17 14:04 ` Eli Zaretskii
2022-10-17 19:31 ` Lars Ingebrigtsen
2022-10-19 16:33 ` Eli Zaretskii
2022-10-17 12:13 ` Lars Ingebrigtsen
2022-10-17 13:47 ` Eli Zaretskii
2022-10-17 19:35 ` Lars Ingebrigtsen [this message]
2022-10-18 7:33 ` Andrea Corallo
2022-10-18 13:51 ` Eli Zaretskii
2022-10-18 18:17 ` Lars Ingebrigtsen
2022-10-18 11:34 ` 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
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=875ygickfw.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58580@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@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).