Re: Enabling native compilation by default when libgccjit is present

[Óscar Fuentes]

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> 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.
>
> My micro-benchmark up there is almost all opaque C primitives, but is
> helped a lot.

I guess nativecomp knows and lowers some of those primitives, i.e. they
are not opaque.

Also, when the primitives are simple, the time used on Elisp "glue code"
that passes results from one primitive to the next can be significant.