Hi! I expanded unsequence check in Clang and found suspicious use volatile qualified variable in several tests:
\clang\test\CodeGen\PowerPC\builtins-ppc-fma.c
\clang\test\CodeGen\PowerPC\builtins-ppc-fpconstrained.c
For C and C++ standards order of evaluate funcall argument is unsequence(or indeterminate sequence) and unsequence access for same volatile variable is UB, but I don’t know if that extends to this compiler builtin.
Volatile forces explicit loads and stores, so I would just expect this to be three separate loads in arbitrary order followed by one store. The reads are unsequenced, but there’s no side-effects without a write, which only happens at the end, which is sequenced. I’m not a language lawyer though.
I think you can ignore the possibility of the built-in having any special semantics that suppresses the undefined behaviour from unsequenced side effects on the same memory location.