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 55945382D83C; Fri, 20 Nov 2020 14:35:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 55945382D83C
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97909] expr_not_equal_to (mainly in match.pd)
 vs. ranger
Date: Fri, 20 Nov 2020 14:35:28 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: 
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-97909-4-f9zRKciwwH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-97909-4@http.gcc.gnu.org/bugzilla/>
References: <bug-97909-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2020 14:35:28 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97909

--- Comment #3 from Andrew Macleod <amacleod at redhat dot com> ---
It should be able to access  the currently known global values that have be=
en
computed, or if there isn't one, it could still go and calculate a global
range.   Which is what the default condition would be (ie, if you don't sup=
ply
a context).

And we can explore under what conditions we can use more info... I suspect
there are times it would be OK and we can supply a context only then.

Regardless, all the on-demand engine does is give you the same information =
you
would have had if you calculated all of it before doing whatever you are ab=
out
to do.   It just avoids the need to do so for anything that isn't relevant.

And if there are times that we can't calculate ranges, then we make sure we
don't.=