unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: mwd@md5i.com, 46502@debbugs.gnu.org, Pip Cet <pipcet@gmail.com>
Subject: bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure
Date: Fri, 19 Feb 2021 14:26:22 +0000	[thread overview]
Message-ID: <xjfv9aom8vl.fsf@sdf.org> (raw)
In-Reply-To: <83ft1s2mp1.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 Feb 2021 15:48:10 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Pip Cet <pipcet@gmail.com>
>> Date: Fri, 19 Feb 2021 13:31:49 +0000
>> Cc: akrl@sdf.org, mwd@md5i.com, 46502@debbugs.gnu.org
>> 
>> > > One thing I've noticed in my experiments is that many builds that are
>> > > interrupted at the wrong point and then resumed produce different
>> > > results. I.e. you type "make", then hit Ctrl-C at the wrong time, then
>> > > type "make" again and you get a different result.
>> >
>> > What does "different result" mean in this case? is the produced .eln
>> > file different? or something else?
>> 
>> There are differences both in the .elc and .eln, and I saw different
>> success/failure behavior but only with local modifications.
>
> Let's talk about *.elc files first, as this is not supposed to happen.
> AFAIR, we write the bytecode into a temporary file, and then rename it
> atomically only when the compilation finishes successfully.  So
> interrupting should not do any harm, and therefore I'm curious what
> kind of differences in *.elc files do you see in these cases.

In native-comp this is very similar, the elc renaming is postponed to be
done when native compilation is done and the temporary eln has been
renamed to its final name.  As eln compilation is triggered by the elc
targets this is supposed to work, or at least it *should* as it does on
master.

  Andrea





  reply	other threads:[~2021-02-19 14:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14  5:05 bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure Michael Welsh Duggan
2021-02-18  9:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 10:14   ` Pip Cet
2021-02-18 10:29     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 14:34     ` Eli Zaretskii
2021-02-19 13:31       ` Pip Cet
2021-02-19 13:48         ` Eli Zaretskii
2021-02-19 14:26           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-02-20  4:35           ` Pip Cet
2021-02-20  8:56             ` Eli Zaretskii
2021-02-20  9:15               ` Pip Cet
2021-02-20 11:21                 ` Eli Zaretskii
2021-02-20 11:48                   ` Eli Zaretskii
2021-02-20 12:03                     ` Pip Cet
2021-02-20 12:42                       ` Eli Zaretskii
2021-02-20 17:00                         ` Pip Cet
2021-02-20 17:18                           ` Eli Zaretskii
2021-02-20 15:42                   ` Stefan Monnier
2021-02-20 17:02                     ` Pip Cet
2021-02-20 17:12                       ` Stefan Monnier
     [not found]                         ` <jwvo8etr7hf.fsf-monnier+emacs@gnu.org>
2021-04-05  2:56                           ` Michael Welsh Duggan
2021-02-18 14:55   ` Michael Welsh Duggan
2021-02-18 15:12     ` 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

  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=xjfv9aom8vl.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=46502@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.org \
    --cc=mwd@md5i.com \
    --cc=pipcet@gmail.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).