diff options
| author | Aldy Hernandez <aldyh@redhat.com> | 2022-10-05 20:22:38 +0200 |
|---|---|---|
| committer | Aldy Hernandez <aldyh@redhat.com> | 2022-10-06 08:21:41 +0200 |
| commit | e9d50e7a4e290d7476cc7e6b5a8f2f1fb496c570 (patch) | |
| tree | 0db52705e95413668e60b84b211f9cdcf8f9cae8 /gcc/dwarf2ctf.cc | |
| parent | 9eab8e45dd106ee6b9ca9fa9ec46876b0bb7f482 (diff) | |
| download | gcc-e9d50e7a4e290d7476cc7e6b5a8f2f1fb496c570.zip gcc-e9d50e7a4e290d7476cc7e6b5a8f2f1fb496c570.tar.gz gcc-e9d50e7a4e290d7476cc7e6b5a8f2f1fb496c570.tar.bz2 | |
Setting explicit NANs sets UNDEFINED for -ffinite-math-only.
We recently agreed that setting a range of NAN should instead set
UNDEFINED for -ffinite-math-only. This patch makes that change to
frange::set_nan() directly. Also, calling frange::update_nan() will now
be a nop for !HONOR_NANS.
Doing this in the setters simplifies everywhere we set NANs, as it keeps
us from introducing NANs by mistake.
gcc/ChangeLog:
* value-range.cc (frange::set): Call set_nan unconditionally.
(range_tests_nan): Adjust tests.
(range_tests_signed_zeros): Same.
(range_tests_floats): Same.
* value-range.h (frange::update_nan): Guard with HONOR_NANS.
(frange::set_nan): Set undefined if !HONOR_NANS.
Diffstat (limited to 'gcc/dwarf2ctf.cc')
0 files changed, 0 insertions, 0 deletions