all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dmitry@gutov.dev, acorallo@gnu.org, stephen.molitor@icloud.com,
	64712@debbugs.gnu.org
Subject: bug#64712: 29.0.92; Emacs 29 with native compilation compiles cl-loaddefs.el on every startup
Date: Tue, 5 Sep 2023 16:11:16 -0700	[thread overview]
Message-ID: <CADwFkmn1_bt-VhQpSVdyAsQ_zT6dTSfnBhevDt9zkLNMGsYcEQ@mail.gmail.com> (raw)
In-Reply-To: <83o7ij96rb.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> Not to slow down the build unnecessarily, I think.  Basically, the
> same reason why we have "no-byte-compile: t" in some files: you get no
> gains from doing that, you just waste CPU time.  And the waste is much
> more significant with native compilation.
>
>> I see that they were added in commit 6c11214dc112, but it doesn't
>> explain why.
>
> When that happens, I always search the mailing lists around the date
> of the commit.  In this case, I found
>
>   https://lists.gnu.org/archive/html/emacs-devel/2022-09/msg00168.html
>
>> I personally can't see that it would make much of a difference if we
>> have them or not, but maybe I'm missing something.
>
> If nothing else, it will slow down startup (because each .eln files
> needs to be loaded via dlopen, as opposed to .elc that is dumped into
> the pdumper file), albeit insignificantly.  But if we do this with all
> the autoload files we have, that could slow down in a more tangible
> ways.  So basically we have here two minor annoyances: you can solve
> one, but then you "gain" the other one.

Right.  So perhaps we should just live with it, and close this as
wontfix.





  reply	other threads:[~2023-09-05 23:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 14:47 bug#64712: 29.0.92; Emacs 29 with native compilation compiles cl-loaddefs.el on every startup Stephen Molitor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 16:34 ` Eli Zaretskii
2023-07-27  1:50   ` Dmitry Gutov
2023-07-27  5:43     ` Eli Zaretskii
2023-07-27  9:03       ` Andrea Corallo
2023-07-27  9:17         ` Eli Zaretskii
2023-07-27  9:56           ` Andrea Corallo
2023-07-27 13:36         ` Dmitry Gutov
2023-07-27 13:52           ` Eli Zaretskii
2023-07-27 16:12             ` Andrea Corallo
2023-07-27 16:25               ` Eli Zaretskii
2023-09-02 21:50               ` Stefan Kangas
2023-09-03  5:15                 ` Eli Zaretskii
2023-09-05 23:11                   ` Stefan Kangas [this message]
2023-09-06 11:29                     ` Eli Zaretskii
2023-09-06 12:09                       ` Stefan Kangas
2023-09-06 12:26                   ` Dmitry Gutov
2023-09-06 13:03                     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADwFkmn1_bt-VhQpSVdyAsQ_zT6dTSfnBhevDt9zkLNMGsYcEQ@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=64712@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=stephen.molitor@icloud.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.