[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Enabling native compilation by default when libgccjit is present
From: |
David Koppelman |
Subject: |
Re: Enabling native compilation by default when libgccjit is present |
Date: |
Thu, 09 Dec 2021 11:00:38 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
> Does it actually give that much of a performance boost?
Native compilation makes a big difference in Gnus. I use Gnus as a mail
reader and its sluggishness was a long time irritant. No more.
Tim Cross <theophilusx@gmail.com> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Po Lu <luangruo@yahoo.com> writes:
>>
>>>> Most distributions will probably release Emacs 28.1 with native
>>>> compilation switched on.
>>>
>>> Why is that so? Most distributions only build their Emacs packages with
>>> the default options.
>>
>> Several distributions have signalled that they want to ship Emacs with
>> native compilation switched on (and at least one said they're going to
>> be doing a full ahead-of-time build, if I remember correctly) --
>> presumably because that'll give their users a faster Emacs.
>
> Does it actually give that much of a performance boost? It has been a
> couple of months since I tried native compilation in Emacs 28, but when
> I did, I noticed next to no performance improvement at all. In fact, all
> I did notice was lots of warnings and significant delays whenever I
> updated packages.
>
> I stopped using it partly because of all the warnings and delays when
> updating packages, but mainly because I seemed to run into a number of
> issues with org mode (most of which I think have now been addressed).
> I've actually never noticed any speed problems with Emacs. Where there
> are delays, it is due to the synchronous nature of what I'm doing rather
> than basic performance. Besides, the slowest component in my environment
> is the old bit of slow carbon using the keyboard :-)
- Re: Enabling native compilation by default when libgccjit is present, (continued)
- Re: Enabling native compilation by default when libgccjit is present, Jim Myhrberg, 2021/12/05
- Re: Enabling native compilation by default when libgccjit is present, Dmitry Gutov, 2021/12/05
- Re: Enabling native compilation by default when libgccjit is present, Jim Myhrberg, 2021/12/05
- Re: Enabling native compilation by default when libgccjit is present, Dmitry Gutov, 2021/12/06
- Re: Enabling native compilation by default when libgccjit is present, João Pedro de Amorim Paula, 2021/12/06
- Re: Enabling native compilation by default when libgccjit is present, Richard Stallman, 2021/12/07
- Re: Enabling native compilation by default when libgccjit is present,
David Koppelman <=
- Re: Enabling native compilation by default when libgccjit is present, Richard Stallman, 2021/12/05
Re: Enabling native compilation by default when libgccjit is present, Michael Heerdegen, 2021/12/03
- Re: Enabling native compilation by default when libgccjit is present, Eli Zaretskii, 2021/12/04
- Re: Enabling native compilation by default when libgccjit is present, Michael Heerdegen, 2021/12/06
- Re: Enabling native compilation by default when libgccjit is present, Michael Heerdegen, 2021/12/07
- Re: Enabling native compilation by default when libgccjit is present, Eli Zaretskii, 2021/12/07
- Re: Enabling native compilation by default when libgccjit is present, Michael Heerdegen, 2021/12/07
- Re: Enabling native compilation by default when libgccjit is present, Robert Pluim, 2021/12/08
- Re: Enabling native compilation by default when libgccjit is present, Michael Heerdegen, 2021/12/08
- Re: Enabling native compilation by default when libgccjit is present, Eli Zaretskii, 2021/12/08