GNU bug report logs -
#75907
30.0.93; Need bigger BASE_PURESIZE when building with PGTK variant
Previous Next
Reported by: Xiyue Deng <manphiz <at> gmail.com>
Date: Tue, 28 Jan 2025 08:40:01 UTC
Severity: normal
Found in version 30.0.93
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Eli Zaretskii <eliz <at> gnu.org> writes:
>> From: Xiyue Deng <manphiz <at> gmail.com>
>> Date: Tue, 28 Jan 2025 00:39:05 -0800
>>
>> When building PGTK variant under Debian sbuild environment (with
>> GCC-14), the build process will fail with "Pure lisp storage overflowed"
>> (more error log at the end of email.) However this seem to happen more
>> likely under this environment only. When using the Debian stable
>> environment with GCC-12 it builds fine, so this looks to be GCC-14
>> related.
>>
>> As it seems historically the value of BASE_PURESIZE is allowed to grow
>> to cope with similar errors, maybe increasing it again is acceptable? I
>> tried that increasing its starting value from 3,000,000 to 5,000,000 to
>> be working, though I haven't tried a smaller value. Patch attached.
>
> Thanks.
>
> Could you find the smallest increment that still allows you to build
> Emacs?
>
Will try to do this and report back.
> Also, what happens if you "make bootstrap" -- do you still need to
> enlarge pure size, or does it build with the current size?
>
Yes, `make bootstrap` still fails with the current size.
(A bit of a longer story: building with `make all` actually failed due to
another error that after a line of "Loading image..." there is an
invalid instruction. It was not until I used `make bootstrap` that I
realize this was the actual issue.)
> And I see you are actually compiling with 30,000,000, which is 10
> times larger than the number you reported:
>
>> -fstack-clash-protection -Wformat -Werror=format-security
>> -fcf-protection -Wall -DBASE_PURESIZE=30000000' 'CPPFLAGS=-Wdate-time
> ^^^^^^^^^^^^^^^^^^^^^^^^
>
> Why is that?
Ah you have sharp eyes! The Emacs I used was built with this size as I
was testing whether this was the cause. I later retried with 5M and it
succeeded as well so I reported that value instead. As mentioned above
I'll continue to try to find the minimal increment.
--
Regards,
Xiyue Deng
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 111 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.