Following up on myself after some further investigation:
>Craig Topper wrote:
>>``*I was thinking about a few less common floating point things and wondered*
>>``*if we need constrained/strict versions of them.*
>>``*-int_fmuladd - which is used by clang to support fp-contract=on where only*
>>``*operations within a statement sare allowed to be concentrated.*
OTOH this is also solely an optimization, so for now we could
simply have clang not generate those when in strict mode.
>I'm also seeing the following additional intrinsics:
>I believe we need a strict version of this as well.
It seems like this is currently only supported on AMDGPU
and will simply trigger an internal error everywhere else.
(I thought there was a default expansion to a multiply
with 1.0 or something, but apparently not ...)
Given that, I don't think we need a strict version
either (at least not straight away).
>This is currently only generated by clang to implement some WebAssembly
>builtins, but adding strict support to parallel maxnum/minnum should
I have a patch for those, which I'll post after ``D71218 ``is in.