diff options
author | Aldy Hernandez <aldyh@redhat.com> | 2022-08-26 16:55:52 +0200 |
---|---|---|
committer | Aldy Hernandez <aldyh@redhat.com> | 2022-08-26 18:12:37 +0200 |
commit | d085901e0e3b3d490fb756b3e939750e7ea2b7fc (patch) | |
tree | c1bc47c06deadc368c9aaf7331bc37f3a012f285 | |
parent | 79db991ece4bf9a63d13c3bce0ed974f3ef859c7 (diff) | |
download | gcc-d085901e0e3b3d490fb756b3e939750e7ea2b7fc.zip gcc-d085901e0e3b3d490fb756b3e939750e7ea2b7fc.tar.gz gcc-d085901e0e3b3d490fb756b3e939750e7ea2b7fc.tar.bz2 |
[ranger] x == -0.0 does not mean we can replace x with -0.0
On the true side of x == -0.0, we can't just blindly value propagate
the -0.0 into every use of x because x could be +0.0.
With this change, we only allow the transformation if
!HONOR_SIGNED_ZEROS or if the range is known not to contain 0.
gcc/ChangeLog:
* range-op-float.cc (foperator_equal::op1_range): Do not blindly
copy op2 range when honoring signed zeros.
-rw-r--r-- | gcc/range-op-float.cc | 17 |
1 files changed, 15 insertions, 2 deletions
diff --git a/gcc/range-op-float.cc b/gcc/range-op-float.cc index ad2fae5..ff9fe31 100644 --- a/gcc/range-op-float.cc +++ b/gcc/range-op-float.cc @@ -252,8 +252,21 @@ foperator_equal::op1_range (frange &r, tree type, switch (get_bool_state (r, lhs, type)) { case BRS_TRUE: - // If it's true, the result is the same as OP2. - r = op2; + if (HONOR_SIGNED_ZEROS (type) + && op2.contains_p (build_zero_cst (type))) + { + // With signed zeros, x == -0.0 does not mean we can replace + // x with -0.0, because x may be either +0.0 or -0.0. + r.set_varying (type); + } + else + { + // If it's true, the result is the same as OP2. + // + // If the range does not actually contain zeros, this should + // always be OK. + r = op2; + } // The TRUE side of op1 == op2 implies op1 is !NAN. r.set_nan (fp_prop::NO); break; |