https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109886
Andrew Macleod <amacleod at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amacleod at redhat dot com
--- Comment #6 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Martin Jambor from comment #5)
> (In reply to Aldy Hernandez from comment #4)
> > (In reply to Andrew Pinski from comment #3)
> > > That is correct. The generated code has a VIEW_CONVERT_EXR from an integer
> > > type to a RECORD_TYPE.
> >
> > Eeeech. In that case, then what you suggest is reasonable. Bail if
> > param_type is not supported by the underlying range. Maybe the IPA experts
> > could opine?
>
> With LTOed type mismateches or with K&R style code, IPA has to be prepared
> to deal with such cases, unfortunately. So a check like that indeed looks
> reasonable.
The new range-op dispatch code is coming shortly.. when an unsupported type is
passed in to any ranger routine, we'll simply return false instead of trapping
like we do now.
