Re: Enabling native compilation by default when libgccjit is present

[Eli Zaretskii]

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Michael Heerdegen <michael_heerdegen@web.de>,  emacs-devel@gnu.org
> Date: Wed, 08 Dec 2021 09:16:46 +0100
> 
> On Dez 07 2021, Eli Zaretskii wrote:
> 
> > You get additional warnings because each of the *.el files is compiled
> > in a separate Emacs process, which starts from a clean state.  By
> > contrast, it may be the case that your code says something like
> >
> >   (require 'foo)
> >   ....
> >   (require 'bar)
> >
> > and 'bar' uses some stuff in 'foo' under the assumption that 'foo' is
> > always loaded before 'bar'.  Since native-compilation will compile
> > 'foo' and 'bar' separately, it will emit warnings.
> 
> This is in no way dependent on native compilation, though.

Not directly, no.  But in most cases, if you byte-compile or load a
file that has these two require's, the require'd files will not be
compiled, definitely not in separate sessions.  Whereas with JIT
native-compilation, both of these do happen.