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, 24 Jan 2022 20:01:01 +0000 [thread overview]
Message-ID: <xjfwnio29aa.fsf@ma.sdf.org> (raw)
In-Reply-To: <xjfk0ep2p8m.fsf@ma.sdf.org> (Andrea Corallo's message of "Mon, 24 Jan 2022 14:16:25 +0000")
Andrea Corallo <akrl@sdf.org> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>> No, you are not misreading. I guess my hypothesis was incorrect, and
>>> something else is at work here. But the problem is real nonetheless.
>>>
>>> Perhaps this is something caused by Alan's speedup of the bootstrap?
>>
>> Could be, but it's affecting a whole lot more files than the ones that
>> were touched by that change... Andrea, can you take a look at this?
>
> Hi Lars,
>
> Hmmm I see what's going on.
>
> The .eln file is produced by 'gcc_jit_context_compile_to_file', we could
> just produce the temporary .elc before calling it and renaming it
> afterwards but unfortunatelly 'gcc_jit_context_compile_to_file' takes a
> considerable part of the compilation time, as a consequence we'd go back
> to the reason this bug was opened for.
>
> I think the best solution is to touch the .eln file once the final .elc
> is produced.
>
> I'll put a patch together.
I've a patch that does that, but is crashing Emacs during bootstrap for
really no reason.
I suspect this is triggering some unrelated bug so I'm trying to see if
I can reproduce it on a sequencial build in order to debug it :/
I'll come with news when I figure out what's going on.
Andrea
next prev parent reply other threads:[~2022-01-24 20:01 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
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 [this message]
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=xjfwnio29aa.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).