From: Andrea Corallo <akrl@sdf.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 58509@debbugs.gnu.org
Subject: bug#58509: 29.0.50; Synchronous nativecomp
Date: Wed, 19 Oct 2022 19:06:28 +0000 [thread overview]
Message-ID: <xjfr0z37hvv.fsf@ma.sdf.org> (raw)
In-Reply-To: <875yghatgo.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 18 Oct 2022 20:15:51 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Andrea Corallo <akrl@sdf.org> writes:
>
> [...]
>
>> (put 'site-run-file 'standard-value '(nil)))
>> + ((equal argi "-no-comp-spawn")
>
> That is not a good command line argument name,
As I mentioned it would be for internal use only, but feel free to offer
a better one.
> and you haven't said why
> you want to introduce yet another command line argument to tweak
> behaviour in this area when we've already discussed adding the
> --native-compile-sync command line argument.
IIUC --native-compile-sync has a different semantic (and it might go in
at a different time as well), this patch is avoid compilation recursion.
I posted it in this bug as (as you mentioned) there was some related
discussion.
Best Regards
Andrea
next prev parent reply other threads:[~2022-10-19 19:06 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 [this message]
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
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=xjfr0z37hvv.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).