x86-64: correct AVX512F vcvtsi2s{d,s} handling
Just like for their AVX counterparts and CVTSI2S{D,S}, a memory source here is ambiguous and hence - in source files should be qualified with a suitable suffix or operand size specifier (not doing so is an error in Intel mode, and will gain a diagnostic in AT&T mode in the future), - in disassembly should be properly suffixed (the Intel operand size specifiers were emitted correctly already).
Showing
- gas/ChangeLog 14 additions, 0 deletionsgas/ChangeLog
- gas/config/tc-i386.c 7 additions, 4 deletionsgas/config/tc-i386.c
- gas/testsuite/gas/i386/avx512f.d 24 additions, 24 deletionsgas/testsuite/gas/i386/avx512f.d
- gas/testsuite/gas/i386/cvtsi2sX.l 9 additions, 0 deletionsgas/testsuite/gas/i386/cvtsi2sX.l
- gas/testsuite/gas/i386/cvtsi2sX.s 14 additions, 0 deletionsgas/testsuite/gas/i386/cvtsi2sX.s
- gas/testsuite/gas/i386/evex-lig256.d 24 additions, 24 deletionsgas/testsuite/gas/i386/evex-lig256.d
- gas/testsuite/gas/i386/evex-lig512.d 24 additions, 24 deletionsgas/testsuite/gas/i386/evex-lig512.d
- gas/testsuite/gas/i386/i386.exp 1 addition, 0 deletionsgas/testsuite/gas/i386/i386.exp
- gas/testsuite/gas/i386/x86-64-avx512f.d 96 additions, 96 deletionsgas/testsuite/gas/i386/x86-64-avx512f.d
- gas/testsuite/gas/i386/x86-64-evex-lig256.d 96 additions, 96 deletionsgas/testsuite/gas/i386/x86-64-evex-lig256.d
- gas/testsuite/gas/i386/x86-64-evex-lig512.d 96 additions, 96 deletionsgas/testsuite/gas/i386/x86-64-evex-lig512.d
- opcodes/ChangeLog 8 additions, 0 deletionsopcodes/ChangeLog
- opcodes/i386-dis-evex.h 8 additions, 8 deletionsopcodes/i386-dis-evex.h
- opcodes/i386-opc.tbl 8 additions, 8 deletionsopcodes/i386-opc.tbl
- opcodes/i386-tbl.h 24 additions, 24 deletionsopcodes/i386-tbl.h
Loading
Please register or sign in to comment