[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#58509: 29.0.50; Synchronous nativecomp
From: |
Eli Zaretskii |
Subject: |
bug#58509: 29.0.50; Synchronous nativecomp |
Date: |
Thu, 20 Oct 2022 11:06:31 +0300 |
> From: Andrea Corallo <akrl@sdf.org>
> Cc: larsi@gnus.org, 58509@debbugs.gnu.org
> Date: Thu, 20 Oct 2022 07:23:55 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Andrea Corallo <akrl@sdf.org>
> >> Cc: larsi@gnus.org, 58509@debbugs.gnu.org
> >> Date: Wed, 19 Oct 2022 19:31:05 +0000
> >>
> >> > "do it always for trampolines in the --batch invocations"
> >>
> >> So you mean identifying that we are doing a trampoline compilation and
> >> disable the native compiler without a specific flag?
> >
> > Yes, but only in -batch sessions.
> >
> > I believe this is our logic now: if we are going to compile a
> > trampoline, we invoke an async subprocess
>
> We invoke a sync compilation for trampolines (but I think it's not
> relevant here)
>
> > with both -batch and
> > the -no-comp-spawn options. But if the --batch session can figure
> > out that it's compiling a trampoline, it can automatically behave as
> > if -no-comp-spawn was passed on the command line, no?
>
> Okay so IIUC your suggestion would be to: when we identify '--batch' we
> search for a signature in the commandline to identify the trampoline
> compilation and set in case `comp-no-spawn'?
Yes. And if that works, my next question is: can we then remove the
new -no-comp-spawn command-line option, or do we need it for some
other cases?
- bug#58509: 29.0.50; Synchronous nativecomp, (continued)
- bug#58509: 29.0.50; Synchronous nativecomp, Eli Zaretskii, 2022/10/18
- bug#58509: 29.0.50; Synchronous nativecomp, Andrea Corallo, 2022/10/19
- bug#58509: 29.0.50; Synchronous nativecomp, Eli Zaretskii, 2022/10/19
- bug#58509: 29.0.50; Synchronous nativecomp, Andrea Corallo, 2022/10/19
- bug#58509: 29.0.50; Synchronous nativecomp, Eli Zaretskii, 2022/10/20
- bug#58509: 29.0.50; Synchronous nativecomp, Andrea Corallo, 2022/10/20
- bug#58509: 29.0.50; Synchronous nativecomp,
Eli Zaretskii <=
- bug#58509: 29.0.50; Synchronous nativecomp, Andrea Corallo, 2022/10/23
- bug#58509: 29.0.50; Synchronous nativecomp, Eli Zaretskii, 2022/10/23
- bug#58509: 29.0.50; Synchronous nativecomp, Andrea Corallo, 2022/10/23
- bug#58509: 29.0.50; Synchronous nativecomp, Andrea Corallo, 2022/10/25
- bug#58509: 29.0.50; Synchronous nativecomp, Eli Zaretskii, 2022/10/25
- bug#58509: 29.0.50; Synchronous nativecomp, Andrea Corallo, 2022/10/26
- bug#58509: 29.0.50; Synchronous nativecomp, Lars Ingebrigtsen, 2022/10/18
- bug#58509: 29.0.50; Synchronous nativecomp, Eli Zaretskii, 2022/10/18
- bug#58509: 29.0.50; Synchronous nativecomp, Eli Zaretskii, 2022/10/18
- bug#58509: 29.0.50; Synchronous nativecomp, Lars Ingebrigtsen, 2022/10/19