From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Enlarge dumped_data[]
Date: Thu, 26 Jan 2023 12:47:01 +0200 [thread overview]
Message-ID: <83bkmlefoa.fsf@gnu.org> (raw)
In-Reply-To: <877cx939km.fsf@yahoo.com> (message from Po Lu on Thu, 26 Jan 2023 17:54:17 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 26 Jan 2023 17:54:17 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Now Emacs dumps correctly if preloaded Lisp has been compiled to
> >> bytecode, but it needs an outrageous 40 megabytes to dump
> >> bootstrap-emacs during bootstrap, so that still fails.
> >>
> >> What changed recently so as to require so much memory?
> >
> > I don't know. Which branch is that, and when did you last build it
> > with the old size of dumped_data?
>
> It worked when I built it around a week ago. It's the master branch,
> emacs-29 builds fine.
Strange. I don't see any obvious candidate. Suggest to bisect. From
12 MB to 40 MB sounds a lot to me, I cannot even begin to think what
kind of change could cause that. Did anything change on your build
system since then? Did you move the source tree to a different place,
perhaps (file names are recorded in the dumped data, so if file names
are longer, you will need more data).
next prev parent reply other threads:[~2023-01-26 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87edrj4fnq.fsf.ref@yahoo.com>
2023-01-25 0:32 ` Enlarge dumped_data[] Po Lu
2023-01-25 12:10 ` Eli Zaretskii
2023-01-25 12:14 ` Po Lu
2023-01-25 13:20 ` Eli Zaretskii
2023-01-25 14:11 ` Po Lu
2023-01-26 1:14 ` Po Lu
2023-01-26 6:55 ` Eli Zaretskii
2023-01-26 9:54 ` Po Lu
2023-01-26 10:47 ` Eli Zaretskii [this message]
2023-01-26 11:44 ` Po Lu
2023-01-26 12:57 ` Eli Zaretskii
2023-01-27 0:42 ` Po Lu
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=83bkmlefoa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.