From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, stefan@marxist.se, 48079@debbugs.gnu.org
Subject: bug#48079: Temporary files while building after native-comp merge
Date: Thu, 06 May 2021 10:12:02 +0000 [thread overview]
Message-ID: <xjfa6p8tbm5.fsf@sdf.org> (raw)
In-Reply-To: <87y2csz0iy.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 06 May 2021 11:15:01 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Andrea Corallo <akrl@sdf.org> writes:
>
>>>> So is it writing the subr.elc0EdJIV file, then doing the .eln
>>>> compilation, and then moving subr.elc0EdJIV to subr.elc?
>>>
>>> Yes, I think so.
>>
>> Confirm.
>
> Again, I haven't actually looked at the code, so this is totally
> uninformed -- but do we have to write the subr.elc0EdJIV file before
> doing the .eln compilation? Can't the .eln compilation work off of the
> contents of a buffer instead?
I think it should be possible, ATM is still the byte-complier saving the
.elc buffer and we delay just the final renaming in comp.el, we could
delay the buffer being saved and do it too after the .eln is produced.
Andrea
next prev parent reply other threads:[~2021-05-06 10:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 11:10 bug#48079: Temporary files while building after native-comp merge Stefan Kangas
2021-04-28 12:10 ` Eli Zaretskii
2021-04-28 12:30 ` Eli Zaretskii
2021-04-28 13:14 ` Stefan Kangas
2021-04-28 19:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-28 21:26 ` Stefan Kangas
2021-04-29 5:14 ` Eli Zaretskii
2021-04-29 8:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 9:20 ` Eli Zaretskii
2021-04-29 10:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-02 23:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-03 17:14 ` Eli Zaretskii
2022-01-06 16:10 ` Andrea Corallo
2022-01-06 16:30 ` Glenn Morris
2022-01-06 16:48 ` Eli Zaretskii
2022-01-06 17:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-07 16:30 ` Andrea Corallo
2022-01-14 15:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 11:22 ` Stefan Kangas
2021-04-29 8:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-02 8:09 ` Lars Ingebrigtsen
2021-05-02 10:12 ` Stefan Kangas
2021-05-02 10:18 ` Lars Ingebrigtsen
2021-05-02 21:36 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 8:35 ` Lars Ingebrigtsen
2021-05-05 12:11 ` Eli Zaretskii
2021-05-05 12:47 ` Lars Ingebrigtsen
2021-05-05 14:01 ` Eli Zaretskii
2021-05-05 14:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-06 9:15 ` Lars Ingebrigtsen
2021-05-06 10:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-04-28 19:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-24 12:36 ` Lars Ingebrigtsen
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=xjfa6p8tbm5.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48079@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).