From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 58509@debbugs.gnu.org
Subject: bug#58509: 29.0.50; Synchronous nativecomp
Date: Wed, 26 Oct 2022 06:40:06 +0000 [thread overview]
Message-ID: <xjflep3f5q1.fsf@ma.sdf.org> (raw)
In-Reply-To: <83fsfbnwor.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Oct 2022 05:30:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: larsi@gnus.org, 58509@debbugs.gnu.org
>> Date: Tue, 25 Oct 2022 19:54:27 +0000
>>
>> >>> The current invocation for compilations is just like:
>> >>>
>> >>> emacs --batch -l sometmpfile.el
>> >>>
>> >>> I don't know if we have some other option for adding a marker other than
>> >>> the most obvious (the dedicated flag).
>> >>
>> >> At some point during compilation, we surely know that we are compiling
>> >> a trampoline, right? So I thought to avoid forking at that point, so
>> >> that we don't need yet another command-line option for internal
>> >> purposes.
>> >
>> > That's correct, but I believe the issue is that when we realize we are
>> > compiling a trampoline it's too late, and we might have been decided
>> > already a new trampoline needs to be compiled and installed. The
>> > parsing of the command line args happens way earlier and that's why this
>> > technique works at solving this issue.
>> >
>> > Andrea
>>
>> What do we want to do? Shall I push my patch that fixes the trampoline
>> bomb with the use of -no-comp-spawn?
>
> Oh, I thought you already did?
>
> Yes, please install that.
Done, into trunk as 5ad5b797f7.
Thanks
Andrea
next prev parent reply other threads:[~2022-10-26 6:40 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 10:38 bug#58509: 29.0.50; Synchronous nativecomp Lars Ingebrigtsen
2022-10-14 10:53 ` Eli Zaretskii
2022-10-14 10:56 ` Lars Ingebrigtsen
2022-10-14 11:04 ` Eli Zaretskii
2022-10-14 11:13 ` Lars Ingebrigtsen
2022-10-14 11:49 ` Eli Zaretskii
2022-10-14 11:51 ` Lars Ingebrigtsen
2022-10-14 11:53 ` Eli Zaretskii
2022-10-14 11:59 ` Lars Ingebrigtsen
2022-10-14 12:11 ` Eli Zaretskii
2022-10-14 12:20 ` Lars Ingebrigtsen
2022-10-14 12:54 ` Eli Zaretskii
2022-10-14 12:59 ` Lars Ingebrigtsen
2022-10-14 13:05 ` Eli Zaretskii
2022-10-14 13:15 ` Lars Ingebrigtsen
2022-10-14 21:40 ` Andrea Corallo
2022-10-15 6:45 ` Eli Zaretskii
2022-10-15 9:22 ` Lars Ingebrigtsen
2022-10-15 16:29 ` Andrea Corallo
2022-10-16 8:50 ` Lars Ingebrigtsen
2022-10-17 7:52 ` Andrea Corallo
2022-10-17 11:20 ` Lars Ingebrigtsen
2022-10-17 11:57 ` Lars Ingebrigtsen
2022-10-17 13:41 ` Eli Zaretskii
2022-10-17 19:30 ` Lars Ingebrigtsen
2022-10-18 13:43 ` Eli Zaretskii
2022-10-18 13:55 ` Andrea Corallo
2022-10-18 18:15 ` Lars Ingebrigtsen
2022-10-19 19:06 ` Andrea Corallo
2022-10-18 18:45 ` Eli Zaretskii
2022-10-19 19:02 ` Andrea Corallo
2022-10-19 19:11 ` Eli Zaretskii
2022-10-19 19:31 ` Andrea Corallo
2022-10-20 6:43 ` Eli Zaretskii
2022-10-20 7:23 ` Andrea Corallo
2022-10-20 8:06 ` Eli Zaretskii
2022-10-23 10:51 ` Andrea Corallo
2022-10-23 11:43 ` Eli Zaretskii
2022-10-23 12:10 ` Andrea Corallo
2022-10-25 19:54 ` Andrea Corallo
2022-10-26 2:30 ` Eli Zaretskii
2022-10-26 6:40 ` Andrea Corallo [this message]
2022-10-18 18:14 ` Lars Ingebrigtsen
2022-10-18 18:32 ` Eli Zaretskii
2022-10-18 18:39 ` Eli Zaretskii
2022-10-19 9:06 ` 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=xjflep3f5q1.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=58509@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/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).