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 302083858D32; Mon, 26 Jun 2023 19:49:34 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 302083858D32
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1687808974;
	bh=/KfG2ciJHIY/9DK5KGLXszVOWL7eFgp6mvkMSZoeVaQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mOL39UCV4yKl1bxm1bBj7IXGqmJTBZgH+CInqEjhtq7NzGf2gQPyvo0XpiuJNGH34
	 l2ZSpFhgVeEkvxe52BbzFVBIRB/SygTT1vwHd4j7GnN6eT9XnuCkYu+1zK5rfCAoLw
	 qWFEzOWBtI74R/owImQ0Fb3TYyH22X6miCMwzcos=
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110377] Early VRP and IPA-PROP should work out value
 ranges from __builtin_unreachable
Date: Mon, 26 Jun 2023 19:49:33 +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: 13.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amacleod at redhat dot com
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-110377-4-whCMKfGITM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110377-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110377-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=3D110377

--- Comment #4 from Andrew Macleod <amacleod at redhat dot com> ---
If I were to guess, I'd guess that its using the default query which simply
picks up global ranges from the global_range_query.

If enable_range() was called at the start, and disable_ranger() at the end =
of
the pass, it would switch to a  context sensitive query.. as long as the IL
isnt going thru too much funny stuff.

My guess is Aldy has been converting the OLD API to rangers API, and simply
hasn't enabled a context ranger yet... Or if he even had plans for that..=
=20=20
Aldy?=