aboutsummaryrefslogtreecommitdiff
path: root/gcc/value-range.h
diff options
context:
space:
mode:
authorAldy Hernandez <aldyh@redhat.com>2022-09-14 08:29:54 +0200
committerAldy Hernandez <aldyh@redhat.com>2022-09-14 17:06:48 +0200
commit4a311a6160b3def190e64ca4a05a03fbcd163598 (patch)
tree34432d6b96408992c4598edeecdf9fe8d676628e /gcc/value-range.h
parent9c4c4186eb7ca0a62fc590edcbb3f8fc9a081e64 (diff)
downloadgcc-4a311a6160b3def190e64ca4a05a03fbcd163598.zip
gcc-4a311a6160b3def190e64ca4a05a03fbcd163598.tar.gz
gcc-4a311a6160b3def190e64ca4a05a03fbcd163598.tar.bz2
Use frange::set_nan() from the generic frange::set().
This patch cleans up the frange::set() code by passing all things NAN to frange::set_nan(). No functional changes. Regstrapped on x86-64 Linux, plus I ran selftests for -ffinite-math-only. gcc/ChangeLog: * value-range.cc (frange::set): Use set_nan. * value-range.h (frange::set_nan): Inline code originally in set().
Diffstat (limited to 'gcc/value-range.h')
-rw-r--r--gcc/value-range.h9
1 files changed, 8 insertions, 1 deletions
diff --git a/gcc/value-range.h b/gcc/value-range.h
index 6e896eb..4392de8 100644
--- a/gcc/value-range.h
+++ b/gcc/value-range.h
@@ -1193,7 +1193,14 @@ frange::set_nan (tree type)
{
REAL_VALUE_TYPE r;
gcc_assert (real_nan (&r, "", 1, TYPE_MODE (type)));
- set (type, r, r);
+ m_kind = VR_RANGE;
+ m_type = type;
+ m_min = r;
+ m_max = r;
+ m_props.set_varying ();
+ m_props.nan_set_yes ();
+ if (flag_checking)
+ verify_range ();
}
// Return TRUE if range is known to be finite.