[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Native compilation on as default?
From: |
Stefan Kangas |
Subject: |
Re: Native compilation on as default? |
Date: |
Wed, 25 Oct 2023 15:48:39 -0700 |
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.
- Re: Native compilation on as default?, Andrea Corallo, 2023/10/25
- Re: Native compilation on as default?, Eli Zaretskii, 2023/10/25
- Re: Native compilation on as default?, Stefan Kangas, 2023/10/25
- Re: Native compilation on as default?, Andrea Corallo, 2023/10/25
- Re: Native compilation on as default?, Stefan Kangas, 2023/10/25
- Re: Native compilation on as default?, Andrea Corallo, 2023/10/25
- Re: Native compilation on as default?,
Stefan Kangas <=
- Re: Native compilation on as default?, Po Lu, 2023/10/25
- Re: Native compilation on as default?, Eli Zaretskii, 2023/10/26
- Re: Native compilation on as default?, Dr. Arne Babenhauserheide, 2023/10/25
- Re: Native compilation on as default?, Eli Zaretskii, 2023/10/26
- Re: Native compilation on as default?, Eli Zaretskii, 2023/10/26
Re: Native compilation on as default?, Richard Stallman, 2023/10/25