Re: Enabling native compilation by default when libgccjit is present

[Michael Heerdegen <michael_heerdegen@web.de>]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Sure, it miscompiles - but it also fails, and a broken eln is never
> loaded.  Only because of that it "works".

What I really wanted to do is to point to the fact that the init file is
a special case.  Will all users be able to fix the warnings so that they
don't get a broken .eln init file?  Will all of them understand what the
problem is - when loading the source works without problems?  Compiled
stuff behaving differently than interpreted code is something that some
people don't expect and understand.

To some degree this is already the case for byte compilation, but users
do that explicitly, or they don't.  I think a significant amount of
Emacs users will have problems fixing the warnings.  We should either
not silently eln compile the users' private files, or find some other
solution, because else we will get a big problem, in my opinion, in the
future: not only complaints, but the barrier for using Emacs would get
higher.  Only programmers would be able to use an Emacs init file.  May
sound funny, but this is not the case today, lot's of people just copy
and paste snippets they find somewhere.  Lot's of people have started
with Emacs exactly this way.

I think eln compiling the user's own files should be opt-in.

Michael.