From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 55BD23858D32; Tue,  2 Jan 2024 20:56:49 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 55BD23858D32
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1704229009;
	bh=F1UPwBOJxCYo09GlbI5ejUdbK7/FBdt4W83ilzYgoZI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=P+BEpU1fhS12WdXJHio6akmzSVWmRxIC8DNwOUDPKf/OQ6Szw5C5pBgwO1EGPG3Op
	 iaj89WDwFUKHlXeubZzIKqCcqslrvU8MPH9LE5ZUEZaCuY5n3mU/4qq1JTkJg5R27v
	 ZWQMtiDUDMQjpxqalK2rnPp2cxYTajLc8e8QNfRA=
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108208] Bad assembly? on large LLVM source files on
 powerpc-unknown-linux-gnu (Error: operand out of range)
Date: Tue, 02 Jan 2024 20:56:47 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: assemble-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108208-4-zfJa9TNlgZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108208-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108208-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108208

--- Comment #10 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-b=
erlin.de> ---
(In reply to Segher Boessenkool from comment #9)
> (In reply to John Paul Adrian Glaubitz from comment #8)
> > (In reply to Segher Boessenkool from comment #7)
> > > This PR is for the sysv ABI, while most discussion was about the "ELF=
v1" ABI.
> >=20
> > Doesn't the subject clearly mention "powerpc-unknown-linux-gnu"?
>=20
> Yes.  And most of the discussion (via the gentoo link) is about
> powerpc64-linux.
>=20
> So things were confusing, for me at least.

OK, yeah. That's confusing. I haven't seen any issues on 64-bit targets.

> > I am trying -O3 now.
>=20
> That almost always runs out of space easier, not less easily.  O3 priorit=
ises
> possible speed wins over anything else (*possible* speed wins).

This actually worked for me and allowed me to build an unregisterised GHC
compiler. So, thanks for the hint!

> > > If you get an error at line 577996 of a source file, changes are your=
 code
> > > is just
> > > completely unreasonably large, esp. on a smaller target like this :-)
> >=20
> > I understand. But it's not always possible to change the code size,
> > especially when the code is not mine but some random upstream code.
> >=20
> > What I don't understand is that other 32-bit architectures don't seem t=
o be
> > affected. For example, hppa-unknown-linux-gnu is not affected.
>=20
> None of the HPPA ABIs are affected by peculiarities of a particular Power=
PC
> ABI.

OK, I see.

> The bug report does noty give enough information to see what is really go=
ing
> on,
> so I have no further advice.

Your pointer towards -O3 did the trick, so no worries!=