From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dmitry Gutov <dmitry@gutov.dev>,
stephen.molitor@icloud.com, 64712@debbugs.gnu.org
Subject: bug#64712: 29.0.92; Emacs 29 with native compilation compiles cl-loaddefs.el on every startup
Date: Thu, 27 Jul 2023 12:12:47 -0400 [thread overview]
Message-ID: <yp1lef1s58g.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83y1j1lavn.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 Jul 2023 16:52:44 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Thu, 27 Jul 2023 16:36:18 +0300
>> Cc: stephen.molitor@icloud.com, 64712@debbugs.gnu.org
>> From: Dmitry Gutov <dmitry@gutov.dev>
>>
>> I suppose another approach would be along the lines of creating, for
>> every such file, an artefact in native-compile cache anyway, with
>> contents which would load the original uncompiled file (I'm assuming
>> this step won't require extracting the file?).
>>
>> Not sure if this is worth the hassle, though.
>
> It definitely isn't.
The closest solution to what Dmitry suggested is to actually remove the
cookie from the file so the eln is produced and we don't try to compile
it anymore. It doesn't harm, again not the most elegant exit strategy
but at least is for free :)
Andrea
next prev parent reply other threads:[~2023-07-27 16:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 14:47 bug#64712: 29.0.92; Emacs 29 with native compilation compiles cl-loaddefs.el on every startup Stephen Molitor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 16:34 ` Eli Zaretskii
2023-07-27 1:50 ` Dmitry Gutov
2023-07-27 5:43 ` Eli Zaretskii
2023-07-27 9:03 ` Andrea Corallo
2023-07-27 9:17 ` Eli Zaretskii
2023-07-27 9:56 ` Andrea Corallo
2023-07-27 13:36 ` Dmitry Gutov
2023-07-27 13:52 ` Eli Zaretskii
2023-07-27 16:12 ` Andrea Corallo [this message]
2023-07-27 16:25 ` Eli Zaretskii
2023-09-02 21:50 ` Stefan Kangas
2023-09-03 5:15 ` Eli Zaretskii
2023-09-05 23:11 ` Stefan Kangas
2023-09-06 11:29 ` Eli Zaretskii
2023-09-06 12:09 ` Stefan Kangas
2023-09-06 12:26 ` Dmitry Gutov
2023-09-06 13:03 ` Eli Zaretskii
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=yp1lef1s58g.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=64712@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=stephen.molitor@icloud.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 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).