On 18/11/2021 11:05, Richard Biener wrote:
+ (if (!flag_trapping_math
+ && direct_internal_fn_supported_p (IFN_TRUNC, type,
+ OPTIMIZE_FOR_BOTH))
+ (IFN_TRUNC @0)))))
#endif
does IFN_FTRUNC_INT preserve the same exceptions as doing
explicit intermediate float->int conversions? I think I'd
prefer to have !flag_trapping_math on both cases.
I realized I never responded to this. The AArch64 instructions mimic the
behaviour you'd see if you were doing explicit conversions, so I'll be
defining the new IFN and optab to require the same, such that these can
be used by the compiler when flag_trapping_math. In the patch I sent
last I added some likes to the md.texi description of the optab to that
intent.
