procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remove range_has_numeric_bounds_p.

Browse source 
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.
This commit is contained in:
Aldy Hernandez 2022-12-21 13:07:54 +01:00
parent ebef388ec3
commit 5db3d28e04
2 changed files with 3 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
gcc/value-range.cc
View file

@ -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

1
gcc/value-range.h
View file

@ -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);