Remove range_has_numeric_bounds_p.

gcc/ChangeLog:

	* value-range.cc (irange::copy_legacy_to_multi_range): Rewrite use
	of range_has_numeric_bounds_p with irange API.
	(range_has_numeric_bounds_p): Delete.
	* value-range.h (range_has_numeric_bounds_p): Delete.

diff --git a/gcc/value-range.cc b/gcc/value-range.cc
index da9098139ad9150489334976fc58ff692f5e5248..f7c3e7a00e2180e0ce1d35e78fcd202256852cdb 100644 (file)
--- a/gcc/value-range.cc
+++ b/gcc/value-range.cc
@@ -979,7 +979,9 @@ irange::copy_legacy_to_multi_range (const irange &src)
     set_varying (src.type ());
   else
     {
-      if (range_has_numeric_bounds_p (&src))
+      if (!src.undefined_p ()
+         && TREE_CODE (src.min ()) == INTEGER_CST
+         && TREE_CODE (src.max ()) == INTEGER_CST)
        set (src.min (), src.max (), src.kind ());
       else
        {
@@ -3068,14 +3070,6 @@ ranges_from_anti_range (const value_range *ar,
   return !vr0->undefined_p ();
 }
 
-bool
-range_has_numeric_bounds_p (const irange *vr)
-{
-  return (!vr->undefined_p ()
-         && TREE_CODE (vr->min ()) == INTEGER_CST
-         && TREE_CODE (vr->max ()) == INTEGER_CST);
-}
-
 /* Return whether VAL is equal to the maximum value of its type.
    We can't do a simple equality comparison with TYPE_MAX_VALUE because
    C typedefs and Ada subtypes can produce types whose TYPE_MAX_VALUE

diff --git a/gcc/value-range.h b/gcc/value-range.h
index c1474a73eafed131f39403ae121c7caac363bf4a..b47540d49bed38f4fe11dfd1e2c98e490b0d701f 100644 (file)
--- a/gcc/value-range.h
+++ b/gcc/value-range.h
@@ -669,7 +669,6 @@ irange::legacy_mode_p () const
   return m_max_ranges == 1;
 }
 
-extern bool range_has_numeric_bounds_p (const irange *);
 extern bool ranges_from_anti_range (const value_range *,
                                    value_range *, value_range *);
 extern value_range_kind get_legacy_range (const irange &, tree &min, tree &max);