Re: Enabling native compilation by default when libgccjit is present

["Jose A. Ortega Ruiz" <jao@gnu.org>]

On Sun, Dec 05 2021, Óscar Fuentes wrote:

> The reason for this is not hard to understand for anyone with a little
> bit of knowledge about binary code optimization. For instance, if your
> Elisp code consists on invoking opaque C primitives, the gain of
> compiling it to machine instructions will be mostly irrelevant.

Well, yes; i am pretty sure that if i went package by package and read
the code i use, the lack of speedups would most probably make sense; but
i find it curious that i am using so little "elisp-heavy" code, given
the variety of contexts in which i use emacs; somehow i was expecting
more what Arthur or Eli report, an overall improvement.  Maybe i'm just
lucky in avoiding cpu intensive pure elisp code (i don't use lsp servers
either), or, more generally, optimizable elisp, and there's in fact a
noticeable effect for most heavy users.  It is interesting that the
patterns can be so markedly different.

Thanks,
jao
-- 
Saying that you don't care about privacy because you don't have
anything to hide is like saying you don't care about freedom of speech
because you have nothing to say. - Edward Snowden