Re: Suppressing native compilation (short and long term)

[Andrea Corallo <akrl@sdf.org>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: rlb@defaultvalue.org, emacs-devel@gnu.org
>> Date: Wed, 28 Sep 2022 18:49:43 +0000
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> From: Andrea Corallo <akrl@sdf.org>
>> >> Cc: emacs-devel@gnu.org
>> >> Date: Wed, 28 Sep 2022 12:52:59 +0000
>> >> 
>> >> This is what `native-comp-deferred-compilation' does.  Well except for
>> >> trampolines but this is extremly light as cpu/energy cost.
>> >
>> > I think if we want to allow people to turn off async compilation, we
>> > should provide a way to force native-comp-available-p to return nil.
>> > When that function returns nil, Emacs already does react correctly (or
>> > at least it's supposed to).
>> 
>> Yes `native-comp-deferred-compilation' AFAIK does exactly this already,
>> `native-comp-available-p' is to check if the native compiler is
>> available (not necessarily the deferred/async mechanism).
>
> But then it should disable the trampolines as well, see startup.el.

Not in my opinion, trampolines are not deferred async compilation.

Also as mentioned ATM is not possible to disable trampolines and have a
fully working native comp Emacs (if we assume primitives can be
redefined).

Best Regards

  Andrea