From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47120@debbugs.gnu.org
Subject: bug#47120: 28.0.50; [feature/native-comp] Stale *.eln files are not recompiled
Date: Sat, 13 Mar 2021 19:43:55 +0000 [thread overview]
Message-ID: <xjfczw22610.fsf@sdf.org> (raw)
In-Reply-To: <83a6r7jxi9.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Mar 2021 09:58:22 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> If you have some *.eln files in your ~/.emacs.d/eln-cache/ directory,
> and the update from Git causes some of the corresponding *.el files to
> be updated, then the *.elc files are rebuilt, but the *.eln files are
> not. Which then leaves you with stale *.eln files in the cache.
>
> Can the FOO.eln file be re-generated if the corresponding FOO.elc file
> is being generated?
FOO.eln should be regenerated when FOO.elc is regenerated using make
*if* FOO.el is part of the files that are native compiled during the
build process (all files when using NATIVE_FULL_AOT).
If this is not what's going on we have a bug.
> And I wonder what happens when we load the corresponding library: will
> the .eln file be preferred even if it's outdated, or will we load the
> .elc file in this situation?
The .elc will be loaded and deferred compilation will spawn an async
native compilation + will do the hot definition swap.
Thanks
Andrea
next prev parent reply other threads:[~2021-03-13 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 7:58 bug#47120: 28.0.50; [feature/native-comp] Stale *.eln files are not recompiled Eli Zaretskii
2021-03-13 19:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-13 19:52 ` Eli Zaretskii
2021-03-13 20:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 20:16 ` Eli Zaretskii
2021-03-13 20:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 20:31 ` Eli Zaretskii
2021-03-13 20:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=xjfczw22610.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=47120@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 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.