On Tue, Jun 3, 2025 at 4:19 PM Spencer Abson wrote:
>
> On Tue, Jun 03, 2025 at 03:26:40PM +0200, Richard Biener wrote:
> > On Tue, Jun 3, 2025 at 3:09 PM Spencer Abson wrote:
> > >
> > > Floating-point to integer conversions can be inexact or invalid (e.g.,
> > > due to
> > > overflow or NaN).
On Tue, Jun 03, 2025 at 03:26:40PM +0200, Richard Biener wrote:
> On Tue, Jun 3, 2025 at 3:09 PM Spencer Abson wrote:
> >
> > Floating-point to integer conversions can be inexact or invalid (e.g., due
> > to
> > overflow or NaN). However, since users of operation_could_trap_p infer the
> > bool
On Tue, Jun 3, 2025 at 3:09 PM Spencer Abson wrote:
>
> Floating-point to integer conversions can be inexact or invalid (e.g., due to
> overflow or NaN). However, since users of operation_could_trap_p infer the
> bool FP_OPERATION argument from the expression's type, the FIX_TRUNC family
> are co
Floating-point to integer conversions can be inexact or invalid (e.g., due to
overflow or NaN). However, since users of operation_could_trap_p infer the
bool FP_OPERATION argument from the expression's type, the FIX_TRUNC family
are considered non-trapping here.
This patch handles them explicitly
