[Bug binutils/13686] New: "objdump -d" does not recognise alternative encodings of lfence/mfence/sfence

2012-02-12 Thread m...@mythic-beasts.com
tatus: NEW Severity: normal Priority: P2 Component: binutils AssignedTo: unassig...@sourceware.org ReportedBy: m...@mythic-beasts.com Classification: Unclassified The canonical encoding of "sfence" is "0f ae f8", but the AMD manual says there

[Bug binutils/13668] x86: objdump gets the wrong length for 66-prefixed direct jumps in 64-bit mode

2012-02-10 Thread m...@mythic-beasts.com
http://sourceware.org/bugzilla/show_bug.cgi?id=13668 --- Comment #2 from Mark Seaborn 2012-02-10 17:08:55 UTC --- Yes, you're right. I was testing on an Intel machine. When I tested on an AMD machine, it produced: $ gcc test.c -o test -m64 && ./test operand size is 2 bytes It looks like Inte

[Bug binutils/13668] New: x86: objdump gets the wrong length for 66-prefixed direct jumps in 64-bit mode

2012-02-06 Thread m...@mythic-beasts.com
Severity: normal Priority: P2 Component: binutils AssignedTo: unassig...@sourceware.org ReportedBy: m...@mythic-beasts.com Classification: Unclassified "objdump -d" produces the following disassembly for x86-64 and shows this "jb" as taking

[Bug gas/13572] New: x86-32: Assembler does not accept "QWORD PTR" for "cvttps2pi" instruction

2012-01-06 Thread m...@mythic-beasts.com
W Severity: normal Priority: P2 Component: gas AssignedTo: unassig...@sourceware.org ReportedBy: m...@mythic-beasts.com Classification: Unclassified There is a discrepancy in binutils between the assembler and disassembler regarding the memo

[Bug binutils/13571] New: objdump incorrectly disassembles 'movnti' as using 'QWORD PTR'

2012-01-06 Thread m...@mythic-beasts.com
Severity: normal Priority: P2 Component: binutils AssignedTo: unassig...@sourceware.org ReportedBy: m...@mythic-beasts.com Classification: Unclassified "objdump -M intel -d" produces the following disassembly for x86-32: 0:0f c3 00