diff options
| author | Aldy Hernandez <aldyh@redhat.com> | 2022-10-14 12:06:56 +0200 |
|---|---|---|
| committer | Aldy Hernandez <aldyh@redhat.com> | 2022-10-14 16:27:40 +0200 |
| commit | 2e252f504b68d001ced53dc1850b67e1368eebc9 (patch) | |
| tree | 62da6252da6282d3b6de8c539be149bf52a53d7d /gcc/value-range.cc | |
| parent | d6a488f243acfac4bdbbb0eefbee3ae916159cf5 (diff) | |
| download | gcc-2e252f504b68d001ced53dc1850b67e1368eebc9.zip gcc-2e252f504b68d001ced53dc1850b67e1368eebc9.tar.gz gcc-2e252f504b68d001ced53dc1850b67e1368eebc9.tar.bz2 | |
Drop -0.0 in frange::set() for !HONOR_SIGNED_ZEROS.
Similar to what we do for NANs when !HONOR_NANS and Inf when
flag_finite_math_only, we can remove -0.0 from the range at creation
time.
We were kinda sorta doing this because there is a bug in
real_isdenormal that is causing flush_denormals_to_zero to saturate
[x, -0.0] to [x, +0.0] when !HONOR_SIGNED_ZEROS. Fixing this bug
(upcoming), causes us to leave -0.0 in places where we aren't
expecting it (the intersection code).
gcc/ChangeLog:
* value-range.cc (frange::set): Drop -0.0 for !HONOR_SIGNED_ZEROS.
Diffstat (limited to 'gcc/value-range.cc')
| -rw-r--r-- | gcc/value-range.cc | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/gcc/value-range.cc b/gcc/value-range.cc index 26a2b78..86550f1 100644 --- a/gcc/value-range.cc +++ b/gcc/value-range.cc @@ -324,6 +324,14 @@ frange::set (tree type, m_neg_nan = false; } + if (!HONOR_SIGNED_ZEROS (m_type)) + { + if (real_iszero (&m_min, 1)) + m_min.sign = 0; + if (real_iszero (&m_max, 1)) + m_max.sign = 0; + } + // For -ffinite-math-only we can drop ranges outside the // representable numbers to min/max for the type. if (flag_finite_math_only) |