Re: Enabling native compilation by default when libgccjit is present

[Eli Zaretskii]

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Wed, 08 Dec 2021 04:39:17 +0100
> 
> Po Lu <luangruo@yahoo.com> writes:
> 
> > But how are those warnings different from what the user will get if he
> > runs `package-install' on a package that causes warnings from the
> > byte-compiler?
> 
> Depends on when these warnings appear.  When they appear as normal side
> effect when installing something, they are not different.  When they
> appear out of nothing, delayed, from a background process, they are
> different because the user not necessarily knows that they are related
> to the installation.

They don't appear out of nothing, they appear because the session
loaded some Lisp.  See my other message.

I suspect this is just something we need to get used to, that's all.
It isn't different in principle from what can happen when you just
load a bunch of Lisp into a running session.