From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>, Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Pure space overflows
Date: Sun, 23 Jan 2022 13:16:05 +0200 [thread overview]
Message-ID: <83mtjmln2i.fsf@gnu.org> (raw)
In-Reply-To: <87v8yarebr.fsf@yahoo.com> (message from Po Lu on Sun, 23 Jan 2022 17:28:24 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 23 Jan 2022 17:28:24 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> powerpc-unknown-linux-gnu needs a SYSTEM_PURESIZE_EXTRA of 250000 to
> >> build without pure space overflows, which seems a little excessive to
> >> me.
> >
> > With what configure options and which optional features?
>
> Sorry, I should've mentioned that it's the same as the other machines I
> tested: XInput 2 and the GTK 3 toolkit, and xpm, jpeg, tiff, gif, png,
> rsvg, and webp support.
>
> Though on that machine, turning XInput 2 off makes no difference.
It is strange that PPC needs significantly more pure space. Does it
have some unique alignment requirements, perhaps?
Andreas, any ideas why additional pure space would be needed for PPC?
next prev parent reply other threads:[~2022-01-23 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pmokustt.fsf.ref@yahoo.com>
2022-01-22 7:34 ` Pure space overflows Po Lu
2022-01-22 8:50 ` Eli Zaretskii
2022-01-22 9:38 ` Po Lu
2022-01-22 10:33 ` Eli Zaretskii
2022-01-22 11:02 ` Po Lu
2022-01-22 11:13 ` Eli Zaretskii
2022-01-22 11:18 ` Eli Zaretskii
2022-01-22 11:19 ` Po Lu
2022-01-23 8:10 ` Po Lu
2022-01-23 8:16 ` Eli Zaretskii
2022-01-23 9:28 ` Po Lu
2022-01-23 11:16 ` Eli Zaretskii [this message]
2022-01-23 12:22 ` Andreas Schwab
2022-01-23 12:39 ` Po Lu
2022-01-23 13:03 ` Andreas Schwab
2022-01-23 13:26 ` Po Lu
2022-01-23 13:35 ` Andreas Schwab
2022-01-24 0:39 ` 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
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=83mtjmln2i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=schwab@linux-m68k.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).