From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: akrl@sdf.org, 58580@debbugs.gnu.org
Subject: bug#58580: 29.0.50; Ahead-of-time compilation for a few more files?
Date: Tue, 18 Oct 2022 13:34:07 +0200 [thread overview]
Message-ID: <87sfjlbc28.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.)
After thinking about this a bit more, I think this is a pretty
compelling argument: Multi-user machines basically don't exist any more,
so there's little to be gained by having the default build do the AOT
for these additional files in the development build.
And distributions will do a full AOT distribution anyway, or will do a
distribution without any .eln file distributed -- it's hard to envision
a distribution doing a distribution with just a handful of .eln files.
So this would just added maintenance burden and further complicate the
build without any gains for users, and I'm therefore closing this bug
report.
prev parent reply other threads:[~2022-10-18 11:34 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
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 [this message]
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=87sfjlbc28.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).