On Fri, Sep 23, 2022 at 9:21 AM Aldy Hernandez wrote:
>
> Ughhh, my bad. I had reworked this as soon as Jakub said we couldn't
> cache the min/max in TYPE_MIN/MAX_VALUE, but forgot to send it. And
> yes...the incessant wrapping was very annoying. It's all fixed.
>
> Let me know what you think.
const_tree type)
> >if (POINTER_TYPE_P (type))
> > return build_zero_cst (const_cast (type));
> >if (frange::supports_p (type))
> > -return build_real (const_cast (type), dconstninf);
> > +{
> > + if (flag_finite_math_only)
> > +
On Thu, Sep 22, 2022 at 6:49 PM Aldy Hernandez wrote:
>
> Similarly to how we drop NANs to UNDEFINED when -ffinite-math-only, I
> think we can drop the numbers outside of the min/max representable
> numbers to the representable number.
>
> This means the endpoings to VR_VARYING for -ffinite-math-o
Similarly to how we drop NANs to UNDEFINED when -ffinite-math-only, I
think we can drop the numbers outside of the min/max representable
numbers to the representable number.
This means the endpoings to VR_VARYING for -ffinite-math-only can now
be the min/max representable, instead of -INF and +INF
