[Bug tree-optimization/68097] We should track ranges for floating-point values too

[aldyh at gcc dot gnu.org]

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

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.
> 
> Note the main part will be to make the FP "range info" available on SSA
> names.
> 
> Other useful queries would include "cannot be Inf/NaN/signed zero".
> 
> Note that transforms based on this (and also nonnegative!) need to be careful
> as there are no data dependences on conditions.  Thus with
> 
>   if (x > 0.)
>    foo (x);
> 
> we may not optimize foo based on 'nonnegative' as code motion has no barrier
> that prevents it from hoisting it before the if.
> 
> 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 currently. 
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.