From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: Noam Postavsky <npostavs@gmail.com>, 15112@debbugs.gnu.org
Subject: bug#15112: 24.3; package.el byte compile autoloads
Date: Thu, 26 Nov 2020 10:34:24 +0100 [thread overview]
Message-ID: <87im9s8nrz.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkmk-cjr=Hhhzjp2-kuBKsfdSrLKenbaPzewsCRaS124Yjg@mail.gmail.com> (Stefan Kangas's message of "Wed, 25 Nov 2020 21:44:41 -0500")
Stefan Kangas <stefan@marxist.se> writes:
Hi Stefan,
> I made a little experiment and of course byte-compiling these files
> gives us a ton of headaches, see below. So I'm not sure this is all
> worth it. Do we have reason to believe that byte-compiling these files
> would give any significant performance increase?
>
> ELC net/tramp-loaddefs.elc
I don't know which kind of experiment you have applied, so I cannot say
anything about the compilation errors. However, I wonder where paths
like "net/tramp-loaddefs.elc" come from. We're speaking about
package.el, meaning we're speaking about ELPA. Tramp in ELPA doesn't use
any subdirectory "net".
Anyway, I don't believe we'll see a performance boost after
byte-compiling loaddef files. They just contain function and variable
declarations, no implementation (but the initial values of variables).
There are exceptions like in tramp-loaddefs.el, but they still don't
count wrt performance, I believe.
Best regards, Michael.
next prev parent reply other threads:[~2020-11-26 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 1:04 bug#15112: 24.3; package.el byte compile autoloads Kevin Ryde
2019-08-28 13:15 ` Stefan Kangas
2019-08-28 14:48 ` Noam Postavsky
2020-11-26 2:44 ` Stefan Kangas
2020-11-26 9:34 ` Michael Albinus [this message]
2020-11-26 10:18 ` Stefan Kangas
2020-11-26 11:53 ` Michael Albinus
2021-01-01 18:56 ` Stefan Kangas
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=87im9s8nrz.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=15112@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=stefan@marxist.se \
/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.