From: Lynn Winebarger <owinebar@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <akrl@sdf.org>,
Lars Ingebrigtsen <larsi@gnus.org>,
Joseph Mingrone <jrm@ftfl.ca>, emacs-devel <emacs-devel@gnu.org>,
emacs@freebsd.org
Subject: Re: --with-native-compilation build failure on 32-bit systems
Date: Thu, 18 Aug 2022 09:47:14 -0400 [thread overview]
Message-ID: <CAM=F=bD3aNW7-FftjQRAeEStui8T=RRnmDEwXVHyS2G0KZ9Taw@mail.gmail.com> (raw)
In-Reply-To: <jwvmtc18yeu.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Thu, Aug 18, 2022, 9:42 AM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> >> - 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).
> >
> > Like I said earlier, I always thought that this problem doesn't affect
> > the pdumper builds. Perhaps that's not true with native-compilation?
>
> I can't see any good reason not to warn about purespace overflow,
> regardless if it leads to misbehavior or not: we clearly do want to size
> the purespace to avoid overflow.
See
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46916
or
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56793
Lynn
[-- Attachment #2: Type: text/html, Size: 1411 bytes --]
next prev parent reply other threads:[~2022-08-18 13:47 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
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 [this message]
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='CAM=F=bD3aNW7-FftjQRAeEStui8T=RRnmDEwXVHyS2G0KZ9Taw@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs@freebsd.org \
--cc=jrm@ftfl.ca \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).