unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: larsi@gnus.org, 52912@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#52912: 29.0.50; Left over files from native compilation
Date: Sat, 22 Jan 2022 12:26:18 +0200	[thread overview]
Message-ID: <83y238m5h1.fsf@gnu.org> (raw)
In-Reply-To: <xjftudz3013.fsf@ma.sdf.org> (message from Andrea Corallo on Wed,  19 Jan 2022 21:09:44 +0000)

> From: Andrea Corallo <akrl@sdf.org>
> Date: Wed, 19 Jan 2022 21:09:44 +0000
> Cc: 52912@debbugs.gnu.org, monnier@iro.umontreal.ca
> 
> Lars Ingebrigtsen <larsi@gnus.org> writes:
> 
> > Andrea Corallo <akrl@sdf.org> writes:
> >
> >> Yes I think we could postpone not only the renaming of the temporary
> >> .elc but also when this is written down.
> >>
> >> I'll try to code up something this week.
> >
> > Great!
> 
> Okay as of 9396b7d0b4 when native compiling we produce the temp .elc
> only just before renaming it, so exactly as we do for simple byte
> compilation.
> 
> This should really minimize this issue to a most likely non observable
> frequency.
> 
> I bootstrapped emacs native and byte compiled and seems to work here.

Looks like this causes trouble, at least when rebuilding Emacs: now
the .elc file is slightly (by 0.1 sec in my case) newer than the
corresponding .eln file, and loadup loads the .elc file instead of
.eln.  If I manually swap the time stamps of the .elc and .eln files,
the problem goes away.

When you bootstrapped the native-compiled Emacs, did you make sure
loadup announced that it was loading "native compiled lisp" files?





  parent reply	other threads:[~2022-01-22 10:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31  5:20 bug#52912: 29.0.50; Left over files from native compilation Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-31 16:10 ` Glenn Morris
2022-01-02 22:35 ` Andrea Corallo
2022-01-15  9:45   ` Lars Ingebrigtsen
2022-01-17 11:07     ` Andrea Corallo
2022-01-17 14:46       ` Andrea Corallo
2022-01-17 14:55         ` Lars Ingebrigtsen
2022-01-19 21:09           ` Andrea Corallo
2022-01-20  8:20             ` Lars Ingebrigtsen
2022-01-20 13:26             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 10:26             ` Eli Zaretskii [this message]
2022-01-22 10:36               ` Lars Ingebrigtsen
2022-01-22 10:46                 ` Eli Zaretskii
2022-01-22 10:50                   ` Lars Ingebrigtsen
2022-01-22 10:56                     ` Eli Zaretskii
2022-01-22 11:20                       ` Lars Ingebrigtsen
2022-01-22 11:28                         ` Eli Zaretskii
2022-01-22 11:46                           ` Lars Ingebrigtsen
2022-01-22 11:51                             ` Eli Zaretskii
2022-01-22 15:50                               ` Lars Ingebrigtsen
2022-01-24 14:16                                 ` Andrea Corallo
2022-01-24 20:01                                   ` Andrea Corallo
2022-01-25 18:18                                     ` Andrea Corallo
2022-01-26 13:41                                       ` Lars Ingebrigtsen
2022-01-27 10:38                                       ` 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=83y238m5h1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52912@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).