unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52912@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#52912: 29.0.50; Left over files from native compilation
Date: Mon, 17 Jan 2022 14:46:14 +0000	[thread overview]
Message-ID: <xjf35lm4dzd.fsf@ma.sdf.org> (raw)
In-Reply-To: <xjf8rve4o3f.fsf@ma.sdf.org> (Andrea Corallo's message of "Mon, 17 Jan 2022 11:07:48 +0000")

Andrea Corallo <akrl@sdf.org> writes:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Andrea Corallo <akrl@sdf.org> writes:
>>
>>> I guess Emacs was brutally killed while building, otherwise we should
>>> clean these.  Not sure how we can do better here, it works exactly as
>>> the byecompiler is working (but is just slower in compiling).
>>
>> I think I've asked this before -- do we have to write the temporary .elc
>> files out to disk at all before doing the .eln compilation?  Can't that
>> work directly from an in-buffer .elc?
>
> I think the same question applies the bytecompiler only:
>
> Do we have to write the temporary .elc files out to disk at all before
> producing and renaming the final .elc?
>
> In general the last action is good to be a file rename as this should be
> atomic.  But that said yes, _when_ we write the temporary file is up to
> us.  Again this is not strictly a native compiler issue, just with the
> native compiler is more likely to be encountered.
>
> Best Regards
>
>   Andrea

Re-reading the whole thread I think I see now what is been suggested.

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.

Thanks

  Andrea






  reply	other threads:[~2022-01-17 14:46 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 [this message]
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
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=xjf35lm4dzd.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=52912@debbugs.gnu.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).