https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110832
--- Comment #8 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Richard Biener from comment #6) > Do we know whether we could in theory improve the sanitizing by optimization > without -funsafe-math-optimizations (I think -fno-trapping-math, > -ffinite-math-only -fno-signalling-nans should be a better guard?)? Regarding the sanitizing, we can remove all sanitizing MOVQ instructions between trapping instructions (IOW, the result of ADDPS is guaranteed to have zeros in the high part outside V2SF, so MOVQ is unnecessary in front of a follow-up MULPS). I think that some instruction back-walking pass on the RTL insn stream would be able to identify these unnecessary instructions and remove them. Also, as mentioned elsewhere, it is really hard to get non-zero value to the highpart of XMM register. The compiler takes great care to always load values via MOVQ, so one has to craft a special code that works around all these fences. OTOH, in two years since gcc-11 was released with the V2SF support, not a single PR involving spurious exceptions was reported. Even capacita benchmark enables: Note: The following floating-point exceptions are signalling: IEEE_UNDERFLOW_FLAG IEEE_DENORMAL without problems. As an example here, it looks that polyhedron capacita greatly benefits from V2SF vectors, and I was surprised that sanitizing MOVQ has such an effect here.
