[Bug binutils/10973] OP_E_memory produces wrong disassembled code

[spop at gcc dot gnu dot org]

------- Additional Comments From spop at gcc dot gnu dot org  2009-11-17 17:07 
-------
Another pattern that objdump does not get right (probably due to
OP_E_memory again) is:

        vfmaddpd       %xmm1,(%ecx,%edi),%xmm6,%xmm4

disassembled like this:

   0:   67                      addr32
   1:   c4                      .byte 0xc4
   2:   e3 49                   jrcxz  0x4d
   4:   69                      .byte 0x69
   5:   24 39                   and    $0x39,%al
   7:   10                      .byte 0x10

It seems like the disassembler expects to read one more byte and then
it gets confused, as in the context of another instruction following
it we get:

        vfmaddpd         %xmm1,(%ecx,%edi),%xmm6,%xmm4
        vfmaddpd         %xmm1,(%ecx,%edi),%xmm6,%xmm4

disassembled like this:

   0:   67 c4 e3 49 69 24 39 10         addr32 vfmaddpd %xmm6,(%esp),%xmm6,%xmm4
   8:   67                      addr32
   9:   c4                      .byte 0xc4
   a:   e3 49                   jrcxz  0x55
   c:   69                      .byte 0x69
   d:   24 39                   and    $0x39,%al
   f:   10                      .byte 0x10





-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10973

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.