https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105763

--- Comment #6 from Andrew Macleod <amacleod at redhat dot com> ---
yeah, from times of yore when the small set of callers made sure it was only
invoked on useful cases.  There were a lot of development asserts from initial
development.

There is no reason to trap, it can simply return false. ie


-  gcc_checking_assert (gimple_range_ssa_p (name));
+  if (!gimple_range_ssa_p (name))
+    return false;

Reply via email to