[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/18738] New: Wrong memory operand size for x86 GATHER/SCATT
From: |
m at rolle dot name |
Subject: |
[Bug binutils/18738] New: Wrong memory operand size for x86 GATHER/SCATTER instructions |
Date: |
Wed, 29 Jul 2015 20:22:55 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=18738
Bug ID: 18738
Summary: Wrong memory operand size for x86 GATHER/SCATTER
instructions
Product: binutils
Version: 2.24
Status: NEW
Severity: minor
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: m at rolle dot name
Target Milestone: ---
objdump disassembles gather/scatter instructions showing the vector operand
size as the memory operand size. However, the Intel doc says it is the element
size.
In these examples:
0: 62 22 7d 41 93 74 b9 vgatherqps ymm30{k1},YMMWORD PTR
[rcx+zmm31*4+0x100]
7: 40
8: 62 22 7d 41 a3 74 b9 vscatterqps YMMWORD PTR
[rcx+zmm31*4+0x100]{k1},ymm30
f: 40
YMMWORD PTR should be DWORD PTR.
(objdump did get the disp*N compression right, converting a 40h displacement
byte into a 0x100 displacement.)
See also bug 18737 for similar problem with gas assembler.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/18738] New: Wrong memory operand size for x86 GATHER/SCATTER instructions,
m at rolle dot name <=