From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, jrm@ftfl.ca, emacs-devel@gnu.org, emacs@FreeBSD.org
Subject: Re: --with-native-compilation build failure on 32-bit systems
Date: Wed, 17 Aug 2022 21:01:48 +0000 [thread overview]
Message-ID: <xjfh72ainyb.fsf@ma.sdf.org> (raw)
In-Reply-To: <xjflermiqtc.fsf@ma.sdf.org> (Andrea Corallo's message of "Wed, 17 Aug 2022 19:59:59 +0000")
Andrea Corallo <akrl@sdf.org> writes:
[...]
> Okay, I had some time to work on this and this is what's going:
>
> After having loaded ediff-hooks temacs never sweeps vectors because,
> even if call `garbage-collect' before dumping, this is inhibited cause
> we overflowed purespace.
>
> Interestingly we warn for purespace overflow calling 'check_pure_size'
> when dumping with unexec and not with pdumper. Given this makes the GC
> not functional (at least in this phase) I'm wondering if we shouldn't do
> this as well.
>
> Also, thinking about the whole system even better, I think fixing-up CUs
> reachable from named functions is definitely a bad for another reason
> that is lambdas! We could have a lambda referenced somewhere that keeps
> a CU loaded and we need to fix it up anyway before dumping.
>
> So yeah I guess tomorrow I'll prepare the patch were we keep a list of
> loaded CU to fix-up.
Right I pushed the fix to scratch/better-cu-fixup so far as:
- I don't know if we want 1a637303b4 and 4bdda39f71 in master or 28.
- I suspect there's some good reason I'm not aware of why we don't
eb539e92e9 at all (this is not necessary to fix the reported issue
tho).
Bests!
Andrea
next prev parent reply other threads:[~2022-08-17 21:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 2:12 --with-native-compilation build failure on 32-bit systems Joseph Mingrone
2022-08-05 11:58 ` Lars Ingebrigtsen
2022-08-05 13:30 ` Andrea Corallo
2022-08-05 14:40 ` Andrea Corallo
2022-08-05 15:16 ` Lynn Winebarger
2022-08-08 7:44 ` Andrea Corallo
2022-08-08 10:22 ` Lynn Winebarger
2022-08-08 13:14 ` Andrea Corallo
2022-08-08 13:55 ` Lynn Winebarger
2022-08-08 14:13 ` Andrea Corallo
2022-08-09 9:11 ` Andrea Corallo
2022-08-09 9:21 ` Andrea Corallo
2022-08-09 9:48 ` Po Lu
2022-08-09 10:03 ` Andrea Corallo
2022-08-09 10:10 ` Po Lu
2022-08-09 10:20 ` Lynn Winebarger
2022-08-09 11:16 ` Eli Zaretskii
2022-08-17 19:59 ` Andrea Corallo
2022-08-17 21:01 ` Andrea Corallo [this message]
2022-08-18 5:30 ` Eli Zaretskii
2022-08-18 8:06 ` Andrea Corallo
2022-08-18 8:15 ` Eli Zaretskii
2022-08-18 9:08 ` Andrea Corallo
2022-08-18 8:31 ` Po Lu
2022-08-18 11:48 ` Joseph Mingrone
2022-08-18 13:40 ` Stefan Monnier
2022-08-18 13:47 ` Lynn Winebarger
2022-08-18 14:49 ` Andrea Corallo
2022-08-18 5:17 ` Eli Zaretskii
2022-08-18 7:59 ` Andrea Corallo
2022-08-18 8:14 ` Eli Zaretskii
2022-08-18 9:06 ` Andrea Corallo
2022-08-18 9:45 ` Eli Zaretskii
2022-08-18 9:57 ` Andrea Corallo
2022-08-18 10:31 ` Eli Zaretskii
2022-08-18 11:08 ` Andrea Corallo
2022-08-18 13:08 ` Eli Zaretskii
2022-08-18 14:09 ` Andrea Corallo
2022-08-18 14:22 ` Eli Zaretskii
2022-08-18 14:50 ` Andrea Corallo
2022-08-18 15:57 ` Eli Zaretskii
2022-08-18 16:42 ` Andrea Corallo
2022-08-18 17:11 ` Eli Zaretskii
2022-08-18 19:35 ` Andrea Corallo
2022-08-19 5:49 ` Eli Zaretskii
2022-08-19 8:11 ` Andrea Corallo
2022-08-09 15:32 ` Lars Ingebrigtsen
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=xjfh72ainyb.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs@FreeBSD.org \
--cc=jrm@ftfl.ca \
--cc=larsi@gnus.org \
/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).