[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/18771] New: objdump incorrectly disassembles 'bndmov', et
From: |
m at rolle dot name |
Subject: |
[Bug binutils/18771] New: objdump incorrectly disassembles 'bndmov', etc., with 32-bit address in 64-bit mode. |
Date: |
Tue, 04 Aug 2015 21:00:58 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=18771
Bug ID: 18771
Summary: objdump incorrectly disassembles 'bndmov', etc., with
32-bit address in 64-bit mode.
Product: binutils
Version: 2.24
Status: NEW
Severity: normal
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: m at rolle dot name
Target Milestone: ---
Related to bug 18770 (for gas). Same confusion as to allowed memory operand
address sizes.
If I assemble "bndmov [eax], bnd1", gas won't allow this, but I can get the
desired effect with a standalone addr prefix..
addr32
bndmov [rax], bndl".
The disassembly will read
67 66 0f 1b 08 addr32 bndmov [rax],bnd1
The correct reading should be
67 66 0f 1b 08 bndmov [eax],bnd1
One aspect of this bug is that if the output code is copied into an assembler
file, that instruction will not assemble. gas will not allow the addr32 on the
same line as the bndmov. I'm sure the desired intent is that the output of
objdump should always assemble back to the original binary code.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/18771] New: objdump incorrectly disassembles 'bndmov', etc., with 32-bit address in 64-bit mode.,
m at rolle dot name <=