From: "Mattias Engdegård" <mattiase@acm.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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 12:45:16 +0200 [thread overview]
Message-ID: <0EFC0B56-47FF-40D2-BC56-0F036CE8CD6C@acm.org> (raw)
In-Reply-To: <jwvv8sz3s0x.fsf-monnier+emacs@gnu.org>
17 juni 2022 kl. 23.27 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
> Indeed, the 64k limit can bite hard in some cases where working around
> it would take a lot of work and we don't have any of the infrastructure
> needed for it.
Right and actually we don't want even to get near that limit because of bad scaling in the compiler.
Stefan, do you agree with the patch (for byte-compile-keep-pending)? I think it's sound but would welcome a second pair of eyes on it.
next prev parent reply other threads:[~2022-06-18 10:45 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 [this message]
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
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=0EFC0B56-47FF-40D2-BC56-0F036CE8CD6C@acm.org \
--to=mattiase@acm.org \
--cc=55972@debbugs.gnu.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).