diff options
| author | Craig Topper <craig.topper@gmail.com> | 2016-09-05 02:20:49 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@gmail.com> | 2016-09-05 02:20:49 +0000 |
| commit | e3807febd8cd519fe019501e868c1234f0dc0b9c (patch) | |
| tree | 8cc78bc065f698bd2f7cc25d9ba0cdb14e24ef7d /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py | |
| parent | 7e1a23001d68893ee10d68e8664021a00fa0bb2c (diff) | |
| download | bcm5719-llvm-e3807febd8cd519fe019501e868c1234f0dc0b9c.tar.gz bcm5719-llvm-e3807febd8cd519fe019501e868c1234f0dc0b9c.zip | |
[X86] Remove FsVMOVAPSrm/FsVMOVAPDrm/FsMOVAPSrm/FsMOVAPDrm. Due to their placement in the td file they had lower precedence than (V)MOVSS/SD and could almost never be selected.
The only way to select them was in AVX512 mode because EVEX VMOVSS/SD was below them and the patterns weren't qualified properly for AVX only. So if you happened to have an aligned FR32/FR64 load in AVX512 you could get a VEX encoded VMOVAPS/VMOVAPD.
I tried to search back through history and it seems like these instructions were probably unselectable for at least 5 years, at least to the time the VEX versions were added. But I can't prove they ever were.
llvm-svn: 280644
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py')
0 files changed, 0 insertions, 0 deletions
