diff options
| author | Craig Topper <craig.topper@gmail.com> | 2016-11-14 01:53:29 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@gmail.com> | 2016-11-14 01:53:29 +0000 |
| commit | b8596e4d1d0fbbd14e1afc7bffb7b7d1cf63f83e (patch) | |
| tree | d6cc7d27286f8e3310071c84d91d1ae9d14c03a0 /llvm/lib/Target/PowerPC/PPCScheduleG4.td | |
| parent | 353e59b6d6339052f3fbf71e793474211a86ed1f (diff) | |
| download | bcm5719-llvm-b8596e4d1d0fbbd14e1afc7bffb7b7d1cf63f83e.tar.gz bcm5719-llvm-b8596e4d1d0fbbd14e1afc7bffb7b7d1cf63f83e.zip | |
[X86] Cleanup 'x' and 'y' mnemonic suffixes for vcvtpd2dq/vcvttpd2dq/vcvtpd2ps and similar instructions.
-Don't print the 'x' suffix for the 128-bit reg/mem VEX encoded instructions in Intel syntax. This is consistent with the EVEX versions.
-Don't print the 'y' suffix for the 256-bit reg/reg VEX encoded instructions in Intel or AT&T syntax. This is consistent with the EVEX versions.
-Allow the 'x' and 'y' suffixes to be used for the reg/mem forms when we're assembling using Intel syntax.
-Allow the 'x' and 'y' suffixes on the reg/reg EVEX encoded instructions in Intel or AT&T syntax. This is consistent with what VEX was already allowing.
This should fix at least some of PR28850.
llvm-svn: 286787
Diffstat (limited to 'llvm/lib/Target/PowerPC/PPCScheduleG4.td')
0 files changed, 0 insertions, 0 deletions
