[LLVMbugs] [Bug 10678] New: [x86 disassembler] vandpd is not disassembled

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=10678

           Summary: [x86 disassembler] vandpd is not disassembled
           Product: libraries
           Version: trunk
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Backend: X86
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: kkhoo at perfwizard.com
                CC: llvmbugs at cs.uiuc.edu


>From the "Intel® 64 and IA-32 Architectures Software Developer’s Manual
Volume 2 (2A & 2B): Instruction Set Reference, A-Z", p. 3-67:

VEX.NDS.128.66.0F.WIG 54 /r
VANDPD xmm1, xmm2, xmm3/m128

VEX.NDS.256.66.0F.WIG 54 /r
VANDPD ymm1, ymm2, ymm3/m256

'VANDPD' can be specified with either the 2- or 3-byte VEX prefix (clang on OSX
correctly assembles the following):

vandpd %xmm2, %xmm1, %xmm3
vandpd %ymm13, %ymm1, %ymm0

The object file shows:
C5 F1 54 DA 
C4 C1 75 54 C5

But using llvm-mc built from trunk revision 135913 produces the wrong output
for these byte sequences:
$ echo '0xc5 0xf1 0x54 0xda'| ./llvm-mc -disassemble -triple="x86_64"
        andps   %xmm2, %xmm3

$ echo '0xc4 0xc1 0x75 0x54 0xc5'| ./llvm-mc -disassemble -triple="x86_64"
        andps   %xmm13, %xmm0

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.