[Bug binutils/10973] OP_E_memory produces wrong disassembled code

2009-11-18 Thread spop at gcc dot gnu dot org
--- Additional Comments From spop at gcc dot gnu dot org 2009-11-19 07:10 --- Fixed. -- What|Removed |Added Status|NEW |RESOLVED

[Bug binutils/10973] OP_E_memory produces wrong disassembled code

2009-11-18 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2009-11-19 07:09 --- Subject: Bug 10973 CVSROOT:/cvs/src Module name:src Changes by: s...@sourceware.org 2009-11-19 07:08:40 Modified files: gas/testsuite : ChangeLog gas/testsuite/gas/

[Bug binutils/10973] OP_E_memory produces wrong disassembled code

2009-11-18 Thread spop at gcc dot gnu dot org
--- Additional Comments From spop at gcc dot gnu dot org 2009-11-18 20:01 --- Yes these are problems linked to how FMA4 and XOP are using OP_E_memory. I am working on a patch to fix these problems. Sebastian -- http://sourceware.org/bugzilla/show_bug.cgi?id=10973 --- You are re

[Bug binutils/10973] OP_E_memory produces wrong disassembled code

2009-11-18 Thread hjl dot tools at gmail dot com
--- Additional Comments From hjl dot tools at gmail dot com 2009-11-18 16:35 --- Those are bugs in FMA4 and XOP patches. -- What|Removed |Added CC|

[Bug binutils/10973] OP_E_memory produces wrong disassembled code

2009-11-17 Thread 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