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 0CD733858D20; Wed,  1 Nov 2023 09:33:38 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CD733858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1698831219;
	bh=7xI3dkBRjanDGNYbRa8w7e//9rS2lNkhTzbgFaWCaIA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=S/rT0GwhqQc9yleCcqWHrzY5nTuuFtqXsBUe4k7e/WZKGttBfsvshiADmFMtfCmv8
	 +uVwxeZIVXE65L/11W/XTsDj3CWO+fQXTu3hJsPnMHBsTBE4+MFUp4bTDHp35m+ohu
	 ly8tzCo4cMpAidRTwkdLeAtj2pM3jhtVM05vFRo0=
From: "chenglulu at loongson dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112330] [14 Regression] LoongArch: LTO bootstrap failure
 with GAS 2.41
Date: Wed, 01 Nov 2023 09:33:38 +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: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chenglulu at loongson dot cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
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-112330-4-grJgqRCh4j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112330-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=3D112330

--- Comment #7 from chenglulu <chenglulu at loongson dot cn> ---
(In reply to Xi Ruoyao from comment #6)
> (In reply to chenglulu from comment #5)
> > (In reply to Xi Ruoyao from comment #4)
> > > (In reply to chenglulu from comment #3)
> > > > (In reply to Xi Ruoyao from comment #1)
> > > > > (In reply to Xi Ruoyao from comment #0)
> > > > >=20
> > > > > > I guess the easiest solution is raising the minimal GAS require=
ment of
> > > > > > bootstrapping GCC 14 on LoongArch to 2.42.
> > > > >=20
> > > > > Another solution might be default to -mno-relax if GAS is 2.41, b=
ut I'm not
> > > > > sure if it's enough.
> > > >=20
> > > > This issue really doesn't happen after adding -mno-relax, but is it=
 really
> > > > necessary to judge the version of binutils because of this?
> > >=20
> > > I'm not sure if -mno-relax is the proper fix.  For now I've reduced t=
he test
> > > case to:
> > >=20
> > > a:
> > > .rept 100000
> > > nop
> > > .endr
> > > beq $r12, $r13, a
> > >=20
> > > but this still does not work with GAS 2.41 even if -mno-relax.
> >=20
> > If this is the assembly code compiled by gcc, then I think it's a gcc b=
ug,
> > although AS shouldn't be an internal error.
>=20
> The internal error issue is fixed by Binutils commit
> f87cf663af71e5d78c8d647fa48562102f3b0615.
>=20
> I think I've over-simplified the test case.  GCC does not generate someth=
ing
> like this.

Uh, I also thought about this gcc and binutils matching issue when I submit=
ted
r14-4674, but I didn't think about whether this should be solved? How to fix
it=EF=BC=9F=