Re: Enabling native compilation by default when libgccjit is present

[Andrea Corallo]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Such warnings usually imply real errors (the resulting file will not
>> work properly because it contains code that "calls" a macro as if it
>> were a function (i.e. after have evaluated the arguments)).
>
> Usually yes, but not for my init file because it is always loaded when I
> compile it.

If you have a specific build sequence that needs to be performed in
other to byte-compile a compilation unit, either you disable native
compilation on this file with the `no-native-compile' cookie, or either
you have to perform the same compilation sequence for native
compilation.

We have synchronous entry points for native compilation that allow you
to load a file and then native compile it (as you do for byte
compilation).

  Andrea