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 2FA1E3853562; Sat, 17 Sep 2022 12:10:29 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2FA1E3853562
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663416629;
	bh=9ZxpYZumMgd1bsgXjn8wvtVy0ZQo/73AEVG6D52v9F8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=YDTiZ9nbFULFXrame0ypd1GhqlbxaOKjo0wkKgYU4KXfazO9tt8UlrM0hrrwaPiU4
	 l3p3KeVdZHEQFqRm8QkB5ps7E90Bfcy/L+lnza0JAwq/kL05SiSqWMmOl/UhCKilM6
	 wonHZqU+PtPWQKjiLXv3EA7KuggkQqUR8t/TOFiA=
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/68097] We should track ranges for
 floating-point values too
Date: Sat, 17 Sep 2022 12:10: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: 6.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-68097-4-ZuYs1oSD67@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68097-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68097-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=3D68097

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldyh at gcc dot gnu.org

--- Comment #6 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> Confirmed.
>=20
> Note the main part will be to make the FP "range info" available on SSA
> names.
>=20
> Other useful queries would include "cannot be Inf/NaN/signed zero".
>=20
> Note that transforms based on this (and also nonnegative!) need to be car=
eful
> as there are no data dependences on conditions.  Thus with
>=20
>   if (x > 0.)
>    foo (x);
>=20
> we may not optimize foo based on 'nonnegative' as code motion has no barr=
ier
> that prevents it from hoisting it before the if.
>=20
> Yes, vectors could also be handled (and yes, please one "value range" per
> SSA name only).  Likewise complex (integer) types.

Is this PR already solved?  FP range info is available on SSA names current=
ly.=20
We can also query inf/NAN/signed zeros/etc.

And regarding PR24021 which pinskia mentioned, there is support for VRP-FP =
now.
 We just don't understand the PLUS_EXPR.  I have a patch for that as well, =
and
should contribute it early next week.=