From: Colin Baxter <m43cap@yandex.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: brickviking <brickviking@gmail.com>, emacs-devel@gnu.org
Subject: Re: Native compilation on as default?
Date: Thu, 26 Oct 2023 13:07:52 +0100 [thread overview]
Message-ID: <8734xxbn8n.fsf@yandex.com> (raw)
In-Reply-To: <yp1fs1xhgaa.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Thu, 26 Oct 2023 05:41:33 -0400")
>>>>> Andrea Corallo <acorallo@gnu.org> writes:
> Colin Baxter <m43cap@yandex.com> writes:
>>>>>>> brickviking <brickviking@gmail.com> writes:
>>
>> > On Thu, 26 Oct 2023 at 15:28, Richard Stallman <rms@gnu.org>
>> wrote > (in part):
>>
>> >> Building Emacs with native compilation is a lot more fragile
>> than >> without. Meanwhile, many users don't need it because
>> Emacs is >> fast enough for us without it.
>> >>
>> >> Theefore, we should not enable native compilation by default.
>> >>
>>
>>
>>
>> > To add to what RMS has stated, I'm on an older machine with not
>> a > lot of room left on the primary partition. I understand
>> that's on > me, but I wanted to add my notes about my local
>> experience.
>>
>> > I compiled Emacs as a test with AOT turned on, and found that
>> it > started creating *.eln files. Lots of them. I recompile
>> Emacs on a > fairly regular basis, and after one compile/install
>> of Emacs, I > noted at least an extra 40Mb after about an hour's
>> running with > erc, org-mode and ef-themes (amongst others). On
>> my older 2008-era > machine that's starting to really show its
>> age, the extra .eln > files were not really worth it for me. I
>> wish I had better news, > I've been wanting a sped-up emacs for a
>> little while now. To be > fair, I _thought_ I saw a speed
>> increase in what amounts to > display code, but I'm not a
>> programmer, mainly a user.
>>
>> > Is there a facility to purge out-of-date versions of the .eln >
>> files for a version that is installed later, and is that facility
>> > easy enough to look for via C-h f? This might make native >
>> compilation easier to swallow.
>>
>> > Regards, brickviking (Emacs 29.1.90, GTK3, Linux-x86_64)
>>
>> I would like to second this. I too run old machines - 15 years
>> old , but still giving good service. I have tried native
>> compilation on one, and noticed only the presence of a large
>> number of extra files with no change in performance. I'm not a
>> developer and don't do anything fancy on emacs.
>>
>> Po makes a very good point. I compile from git and only one
>> machine has the necessary library (or libraries?)
>>
>> Best wishes,
>>
>> Colin Baxter.
> Hi Colin,
> again, the proposal (see original message) is to have it on by
> default *only* when libgccjit is available. I bet you don't have
> it installed on those machines as AFAIK the only SW in production
> that uses it is Emacs.
Well, I do have libjccjit-6-dev on a machine running Debian 9.13. This
is the machine on which I did try native compilation. As I said, I could
see zero change in performance of my emacs (30.0.50). There's also
libjccjit-8 on another machine of mine running Debian 10.13.
I now always compile with "--with-native-compilation=no". Are you saying
that this configure option will not in the future be sufficient and I
will have to make sure there's no libjccjit versions on the system?
Best wishes, Colin.
next prev parent reply other threads:[~2023-10-26 12:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 8:44 Native compilation on as default? Andrea Corallo
2023-06-09 11:23 ` Eli Zaretskii
2023-06-09 16:56 ` Andrea Corallo
2023-06-09 17:22 ` Eli Zaretskii
2023-10-25 14:11 ` Andrea Corallo
2023-10-25 14:18 ` Eli Zaretskii
2023-10-25 14:42 ` Stefan Kangas
2023-10-25 20:50 ` Andrea Corallo
2023-10-25 21:22 ` Stefan Kangas
2023-10-25 21:33 ` Andrea Corallo
2023-10-25 22:48 ` Stefan Kangas
2023-10-26 0:32 ` Po Lu
2023-10-26 6:39 ` Eli Zaretskii
2023-10-26 3:47 ` Dr. Arne Babenhauserheide
2023-10-26 7:13 ` Eli Zaretskii
2023-10-26 4:58 ` Eli Zaretskii
2023-11-20 9:41 ` Andrea Corallo
2023-11-20 12:20 ` Eli Zaretskii
2023-11-20 22:21 ` Emanuel Berg
2023-11-21 10:39 ` Andrea Corallo
2023-11-21 10:38 ` Andrea Corallo
2023-10-26 2:27 ` Richard Stallman
2023-10-26 3:55 ` brickviking
2023-10-26 7:20 ` Eli Zaretskii
2023-10-26 7:36 ` Colin Baxter
2023-10-26 9:41 ` Andrea Corallo
2023-10-26 12:07 ` Colin Baxter [this message]
2023-10-26 12:14 ` Andrea Corallo
2023-10-26 13:02 ` Eli Zaretskii
2023-10-27 7:08 ` Colin Baxter
2023-10-26 14:22 ` Emanuel Berg
2023-10-27 14:41 ` Gregor Zattler
2023-10-26 6:44 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2024-02-29 10:56 Andrea Corallo
2024-02-29 13:39 ` Eli Zaretskii
2024-02-29 15:07 ` Andrea Corallo
2024-02-29 16:26 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734xxbn8n.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=acorallo@gnu.org \
--cc=brickviking@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).