Re: Native compilation on as default?

[Po Lu]

Stefan Kangas <stefankangas@gmail.com> writes:

> Andrea Corallo <acorallo@gnu.org> writes:
>
>> doing some work I just re-discovered that a good a explaination of that
>> was written by Eli in the 'native-comp-async-report-warnings-errors' doc
>> :)
>>
>> "
>> When native compilation happens asynchronously, it can produce
>> warnings and errors, some of which might not be emitted by a
>> byte-compilation.  The typical case for that is native-compiling
>> a file that is missing some ‘require’ of a necessary feature,
>> while having it already loaded into the environment when
>> byte-compiling.
>>
>> As asynchronous native compilation always starts from a pristine
>> environment, it is more sensitive to such omissions, and might be
>> unable to compile such Lisp source files correctly.
>
> Thanks for the reminder.  So I think the plan you outlined previously
> sounds good.

I'm not opposed to this in principle, but two precautions are
prerequisite for instituting such a change.  First, the configure script
must arrange for native compilation to be disabled if libgccjit is
unavailable (or else ./configure && make will no longer work); and
second, I think it should be disabled when building from the Git
repository, for native compilation delays making the Lisp directory by a
length of time that is unacceptable for Emacs development.