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 6714A3865479; Thu,  9 May 2024 21:54:57 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6714A3865479
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1715291697;
	bh=1xTpa+DR7yDFrVQ3otc6N14b7/Ic+9Q8xMB6faRY+4s=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=wnNaeOzi5wTFVB0U65iE7Ei2bosUXz37GNIR+hITvw6mYxqlMbn5HPk4ycsR1Ynrj
	 /X0lp50uQIdi6E8iCs49j7jlJXAr4Ser9MUrlH9BQWA43f9CJNHBJc1oVBEWezkF4+
	 qep+7kNINd4ymwzcUwEOR11OdEZ60uagrqZ7Gn8s=
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/114985] [15 regression] internal compiler error: in
 discriminator_fail during stage2
Date: Thu, 09 May 2024 21:54:56 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 15.0
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aldyh 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: 15.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-114985-4-ZmyW0EcDtv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114985-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=3D114985

--- Comment #10 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to David Edelsohn from comment #9)
> The patch in comment 6 succeeds for me, but it seems more of a heavy-hand=
ed
> band-aid that confirms the symptom, but covers up the problem.
>=20
> Something in GCC apparently has generated invalid IR that was not caught
> earlier.  GCC should not generate
>=20
> POINTER =3D POINTER CMP POINTER
>=20
> But the trunk should not be left in a broken state as per GCC development
> policy.  The broken trunk interferes with the work of other developers and
> may mask other broken patches being committed.
>=20
> This patch should be reverted until the source of the problem is discover=
ed
> and fixed.

The range request is not necessarily coming from the IR, but it is a request
that the IPA pass is making of the ranger, which does adhere by gimple IR
rules.  So this may not be bad IR, but just a quirk of how IPA makes reques=
ts
of the ranger.  As such, I don't think it's heavy handed, but we do need the
IPA experts to opine.=