unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 55972@debbugs.gnu.org, Lynn Winebarger <owinebar@gmail.com>
Subject: bug#55972: 28.1; Package quickstart generated for large number of packages generates byte-code string larger than 64K, triggering bytecode overflow error
Date: Sat, 18 Jun 2022 10:53:02 -0400	[thread overview]
Message-ID: <jwvtu8iyqki.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8E7F9A90-3A32-46D9-9B25-E71DB0A820BC@acm.org> ("Mattias Engdegård"'s message of "Sat, 18 Jun 2022 15:53:12 +0200")

> To solve the problem entirely, it's possible that we also need to split the
> top-level `let` forms in package-quickstart.el.

I think the other bug (about `autoload` calls that define macros
leading to warnings because they're not at top-level) suggests that we
should move the calls to `autoload` outside of the `let`, which would
probably make this problem even less likely.

> For instance, `magit` generates a 5 KiB bytecode chunk and 750-element
> constant vector which is perfectly manageable, but a package with more
> autoloads may be troublesome. Do you know a package that would fit
> the description?

I suspect none.  I suspect in the case of Magit the magit-autoloads.el
file is actually too large for its own good: it should probably be split
into autoloads that "face outside" (i.e. those that need to be defined
before Magit is used) from those facing inside (those that are needed
for internal lazy loading).

The old autoload.el didn't support this conveniently, but the new one
does, so a few years from now we'll have a clean solution :-)


        Stefan






  reply	other threads:[~2022-06-18 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 14:51 bug#55972: 28.1; Package quickstart generated for large number of packages generates byte-code string larger than 64K, triggering bytecode overflow error Lynn Winebarger
2022-06-14 16:29 ` Mattias Engdegård
2022-06-15  9:31   ` Mattias Engdegård
2022-06-17 20:06   ` Lynn Winebarger
2022-06-17 21:27     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-18 10:45       ` Mattias Engdegård
2022-06-18 12:59         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-18 13:53           ` Mattias Engdegård
2022-06-18 14:53             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-13  1:37               ` Stefan Kangas
2023-09-13 14:52                 ` Jonas Bernoulli via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 14:58                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=jwvtu8iyqki.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55972@debbugs.gnu.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=owinebar@gmail.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 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).