unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: brickviking <brickviking@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Native compilation on as default?
Date: Thu, 26 Oct 2023 16:55:08 +1300	[thread overview]
Message-ID: <CAHWye85pk9CuPYLuEJimbd7mrW9QHZpNd9bx=eCir_cigbt6Dg@mail.gmail.com> (raw)
In-Reply-To: <E1qvq5V-0002uL-Ib@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]

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)

[-- Attachment #2: Type: text/html, Size: 1829 bytes --]

  reply	other threads:[~2023-10-26  3:55 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 [this message]
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
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='CAHWye85pk9CuPYLuEJimbd7mrW9QHZpNd9bx=eCir_cigbt6Dg@mail.gmail.com' \
    --to=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).