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 F414A3857C72; Fri, 16 Feb 2024 17:01:54 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F414A3857C72
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1708102915;
	bh=VlTW4zcZQXiJ5UyFPuWWNMJbwtTS6+WnB6nffYSY1zs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=A6juuti1OG+nhD3xRD6Eq7xVv/1pNylyotaLC7R5+bHG/ESLeQC2ILr6JdqwR1bHs
	 xXoUh/ENkhnTUVrQ83NUPcmeAC4/ivkZs4pF+VTC+AK+xZMT6qNALcGU7NHeeG/Q1M
	 BnbU63sgHEkobm2c6wQ4mCcxLypTekYpOvOITDxI=
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113907] [12/13/14 regression] ICU miscompiled since
 on x86 since r14-5109-ga291237b628f41
Date: Fri, 16 Feb 2024 17:01:54 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amacleod at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113907-4-sRrrGpwude@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113907-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113907-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=3D113907

--- Comment #46 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Jan Hubicka from comment #43)
> > // See discussion here:
> > // https://gcc.gnu.org/pipermail/gcc-patches/2021-June/571709.html
> Discussion says:
>=20
> "Once legacy evrp is removed, this won't be an issue, as ranges in the IL=
=20
> will tell the truth.  However, this will mean that we will no longer=20
> remove the first __builtin_unreachable combo.  But ISTM, that would be=20
> correct behavior ??."
>=20
> So perhaps, we could remove that special case for default def and phi?
> It is an odd thing and we clearly lose info here.
>=20

legacy VRP has been removed now.  So in theory we are free to do as we want=
..
but I don't remember the specific details.

So do you just want to always use get_range_global() ?  and not do the chec=
k?

I can try changing it to just get_global  and see what happens.=