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 C50F83858C2B; Mon, 23 Oct 2023 14:53:44 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C50F83858C2B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1698072824;
	bh=lmOTBWw60IqujhAfcb1D5I/t+vqZ+WfT1D0E/M4DOOQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=oZTmn1NBLTDf2Q6Xl6JJepz99MVWy9obVtK385RgSuVDKeTr97cLKk3gEyi1De6mY
	 y8KS7+2VIDN9KfyXbSW6NC9OH0N4YvGX5ixKtlbYlQP8zDFRIh8WKa9VPcPqS+qPg9
	 OolWLz8uFkBw1hDTKGRLcRqHDieF9ZbPEUCv8RGA=
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111001] SH: ICE during RTL pass: sh_treg_combine2
Date: Mon, 23 Oct 2023 14:53:44 +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.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-111001-4-jYZi2qvL0l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111001-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111001-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=3D111001

--- Comment #17 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to John Paul Adrian Glaubitz from comment #16)

> Just saw the branch updates, thanks! FWIW, I did observe this issue in
> gcc-13 only but not gcc-11 or gcc-12. But that might be owed to the fact
> that Debian's gcc-11 and gcc-12 packages had not received the latest bran=
ch
> updates yet.

Yes, I know it has been observed on the latest GCC-13 only.  It was an
oversight in the code from the beginning, which got triggered by another ch=
ange
in the compiler.  I haven't checked which change exactly, but I guess it mu=
st
have been some backported change. So if the same/similar thing gets backpor=
ted
to GCC-11 or GCC-12 it might trigger this bug there, too.  Hence the preven=
tive
measure.  It's a rather obvious bug/fix, so should be safe.=