aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAldy Hernandez <aldyh@redhat.com>2023-04-23 08:04:55 +0200
committerAldy Hernandez <aldyh@redhat.com>2023-04-23 11:02:42 +0200
commit5830953a446959c5d8d9b569ffcd3e3bb16a06dc (patch)
tree8eefcc98b6380603e6c17ab01ecac0868a0f0244
parent525713ed9db904ed2504decc5bde9d58bd5d98b4 (diff)
downloadgcc-5830953a446959c5d8d9b569ffcd3e3bb16a06dc.zip
gcc-5830953a446959c5d8d9b569ffcd3e3bb16a06dc.tar.gz
gcc-5830953a446959c5d8d9b569ffcd3e3bb16a06dc.tar.bz2
Handle NANs in frange::operator== [PR109593]
This patch... commit 10e481b154c5fc63e6ce4b449ce86cecb87a6015 Return true from operator== for two identical ranges containing NAN. removed the check for NANs, which caused us to read from m_min and m_max which are undefined for NANs. gcc/ChangeLog: PR tree-optimization/109593 * value-range.cc (frange::operator==): Handle NANs.
-rw-r--r--gcc/value-range.cc10
1 files changed, 10 insertions, 0 deletions
diff --git a/gcc/value-range.cc b/gcc/value-range.cc
index 17f4e1b..9716241 100644
--- a/gcc/value-range.cc
+++ b/gcc/value-range.cc
@@ -682,6 +682,16 @@ frange::operator== (const frange &src) const
if (varying_p ())
return types_compatible_p (m_type, src.m_type);
+ bool nan1 = known_isnan ();
+ bool nan2 = src.known_isnan ();
+ if (nan1 || nan2)
+ {
+ if (nan1 && nan2)
+ return (m_pos_nan == src.m_pos_nan
+ && m_neg_nan == src.m_neg_nan);
+ return false;
+ }
+
return (real_identical (&m_min, &src.m_min)
&& real_identical (&m_max, &src.m_max)
&& m_pos_nan == src.m_pos_nan