From 25dd2768afdb8fad7b11d511eb5f739958f9870d Mon Sep 17 00:00:00 2001 From: Aldy Hernandez Date: Wed, 31 Aug 2022 12:09:44 +0200 Subject: Stream out endpoints for frange. We only stream out the FP properties for global float ranges (currently only NAN). The following patch adds the endpoints as well. gcc/ChangeLog: * value-range-storage.cc (frange_storage_slot::set_frange): Save endpoints. (frange_storage_slot::get_frange): Restore endpoints. * value-range-storage.h (class frange_storage_slot): Add endpoint fields. --- gcc/value-range-storage.cc | 18 +++++++----------- gcc/value-range-storage.h | 8 +++++--- 2 files changed, 12 insertions(+), 14 deletions(-) diff --git a/gcc/value-range-storage.cc b/gcc/value-range-storage.cc index 4943927..b7a23fa 100644 --- a/gcc/value-range-storage.cc +++ b/gcc/value-range-storage.cc @@ -253,6 +253,8 @@ frange_storage_slot::set_frange (const frange &r) gcc_checking_assert (fits_p (r)); gcc_checking_assert (!r.undefined_p ()); + m_min = r.m_min; + m_max = r.m_max; m_props = r.m_props; } @@ -261,18 +263,12 @@ frange_storage_slot::get_frange (frange &r, tree type) const { gcc_checking_assert (r.supports_type_p (type)); - // FIXME: NANs get special treatment, because we need [NAN, NAN] in - // the range to properly represent it, not just the NAN flag in the - // property bits. This will go away when we stream out the - // endpoints. - if (m_props.get_nan ().yes_p ()) - { - r = frange_nan (type); - return; - } - - r.set_varying (type); + r.set_undefined (); + r.m_kind = VR_RANGE; r.m_props = m_props; + r.m_type = type; + r.m_min = m_min; + r.m_max = m_max; r.normalize_kind (); if (flag_checking) diff --git a/gcc/value-range-storage.h b/gcc/value-range-storage.h index 9cd6b9f..f506789 100644 --- a/gcc/value-range-storage.h +++ b/gcc/value-range-storage.h @@ -113,9 +113,11 @@ class GTY (()) frange_storage_slot frange_storage_slot (const frange &r) { set_frange (r); } DISABLE_COPY_AND_ASSIGN (frange_storage_slot); - // We can get away with just storing the properties because the type - // can be gotten from the SSA, and UNDEFINED is unsupported, so it - // can only be a range. + // We can get away with just storing the properties and the + // endpoints because the type can be gotten from the SSA, and + // UNDEFINED is unsupported, so it can only be a VR_RANGE. + REAL_VALUE_TYPE m_min; + REAL_VALUE_TYPE m_max; frange_props m_props; }; -- cgit v1.1