[X86] Add test RUN lines to show cases where we use 512-bit vcmppd/ps with...
[X86] Add test RUN lines to show cases where we use 512-bit vcmppd/ps with garbage upper bits for 128/256-bit strict_fsetcc On KNL targets, we widen 128/256-bit strict_fsetcc nodes to 512-bits without forcing the upper bits to zero. This can cause spurious exceptions due to garbage upper bits. This behavior was inherited from the non-strict case where the spurious exception isn't a problem.
Loading
Please sign in to comment