diff options
| author | Craig Topper <craig.topper@gmail.com> | 2020-02-12 20:39:30 -0800 |
|---|---|---|
| committer | Craig Topper <craig.topper@gmail.com> | 2020-02-12 20:51:52 -0800 |
| commit | af15082af42020c155144103cb345ae54f02b39f (patch) | |
| tree | c877ba9a9eceb6434330efbf3e865927021a0f9a /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp | |
| parent | 61bd33e37b1d4f3feda50162ec196e5e14759686 (diff) | |
| download | llvm-af15082af42020c155144103cb345ae54f02b39f.zip llvm-af15082af42020c155144103cb345ae54f02b39f.tar.gz llvm-af15082af42020c155144103cb345ae54f02b39f.tar.bz2 | |
[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.
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions