Re: Enabling native compilation by default when libgccjit is present

[T.V Raman]

Michael Heerdegen <michael_heerdegen@web.de> writes:


Note also that there isn't a 1:1 correspondence between bytecomp
warnings, ie when going from el->elc vs native comp ie when going  from
el->eln.

To ensure equivalence  I believe we need to go from elc->eln.

The emacs dev contract (implicit) has always been el->elc and developers
 should feel responsible for fixing el->elc warnings. But given the
 large number of already launched packages, changing that contract now
 to say developers should fix el->eln warnings is unlikely to succeed
 in the large.

> 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.
>
> Most packages installed here were installed before turning native comp
> on.  Maybe the experience is different when installing stuff after
> switching, I haven't checked.  But lots of regular
> (non-Emacs-developer) users will undergo the same switch some time in
> the future, with already installed packages. 
>
> Michael.
>
>

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
?7?4 Id: kg:/m/0285kf1  ?0?8