Re: --with-native-compilation build failure on 32-bit systems

[Eli Zaretskii]

> From: Andrea Corallo <akrl@sdf.org>
> Cc: larsi@gnus.org, jrm@ftfl.ca, emacs-devel@gnu.org, emacs@FreeBSD.org
> Date: Thu, 18 Aug 2022 14:09:45 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Andrea Corallo <akrl@sdf.org>
> >> Cc: larsi@gnus.org, jrm@ftfl.ca, emacs-devel@gnu.org, emacs@FreeBSD.org
> >> Date: Thu, 18 Aug 2022 11:08:32 +0000
> >> 
> >> On 64bit I get:
> >> 
> >> emacs:0:Pure Lisp storage overflow (approx. 3366891 bytes needed)
> >> 
> >> On 32:
> >> 
> >> emacs:0:Pure Lisp storage overflow (approx. 2549794 bytes needed)
> >
> > That's soooo strange!  If I start Emacs under GDB and print the value
> > of PURESIZE, I get 6000000 bytes in a 64-bit build and 4480000 bytes
> > in a 32-bit build --with-wide-int.  What values do you see?
> >
> > Maybe the problem happens only in --without-x builds?
> 
> I get 2000000 on the 32bit build and 3333333 on 64 bit.  Both are indeed
> --without-x.  According a to comment in puresize.h this has an effect.

What is the value of SYSTEM_PURESIZE_EXTRA in both cases?