[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 14:22:31 -0700 |
Andrea Corallo <acorallo@gnu.org> writes:
> Thinking about this... IME *the* warning we are interested in from the
> async compilation is the:
>
> "the function ‘xxx’ is not known to be defined."
>
> This because typically xxx is not a function but a macro and is unknown
> due to a missing require, the file end-up misscompiled and not
> functional.
What is it specifically that makes this into a separate issue for the
native-compiler? Shouldn't the byte-compiler also warn about a
situation like that?
- 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 <=
- 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?, 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