diff options
| author | Aldy Hernandez <aldyh@redhat.com> | 2022-10-22 16:22:50 +0200 |
|---|---|---|
| committer | Aldy Hernandez <aldyh@redhat.com> | 2022-10-22 16:26:05 +0200 |
| commit | 423df44a090846b9c59650efb11745f07914f1d5 (patch) | |
| tree | cf9f2b56a3cf8c7ba634065d0ca52787d04512c9 /gcc | |
| parent | e0927d7ddca154b1a5151da698e205593cb8912e (diff) | |
| download | gcc-423df44a090846b9c59650efb11745f07914f1d5.zip gcc-423df44a090846b9c59650efb11745f07914f1d5.tar.gz gcc-423df44a090846b9c59650efb11745f07914f1d5.tar.bz2 | |
Update selftest such that [-Inf, +Inf] is always VARYING for -ffinite-math-only.
[-Inf, +Inf] +-NAN gets normalized as VARYING. There is a test that
drops the NAN possibility, and tests that the range is no longer
VARYING but [-Inf, +Inf]. However, for -ffinite-math-only targets
(Vax, RX, etc) the range would still be VARYING because the VARYING
range never had a NAN to begin with. This fixes the test.
I have a precommit hook that does self-tests with
-fno-finite-math-only, -ffinite-math-only, and -ffast-math as a sanity
check, but my precommit hook last week was disabled because there was
a tree-ssa.exp in mainline failing which was throwing off my scripts.
My apologies.
gcc/ChangeLog:
* value-range.cc (range_tests_floats): Predicate [-Inf, +Inf] test
with !flag_finite_math_only.
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/value-range.cc | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/gcc/value-range.cc b/gcc/value-range.cc index bcda498..d779e98 100644 --- a/gcc/value-range.cc +++ b/gcc/value-range.cc @@ -3960,8 +3960,11 @@ range_tests_floats () if (r0.maybe_isnan ()) ASSERT_TRUE (r0.varying_p ()); // ...unless it has some special property... - r0.clear_nan (); - ASSERT_FALSE (r0.varying_p ()); + if (!flag_finite_math_only) + { + r0.clear_nan (); + ASSERT_FALSE (r0.varying_p ()); + } // For most architectures, where float and double are different // sizes, having the same endpoints does not necessarily mean the |