This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
RE: PATCH: Move operand/address-size override prefixes before SIMD prefix
- From: malc <av1474 at comtv dot ru>
- To: "Menezes, Evandro" <evandro dot menezes at amd dot com>
- Cc: Jan Beulich <jbeulich at novell dot com>, "H. J. Lu" <hjl at lucon dot org>, binutils at sourceware dot org
- Date: Thu, 7 Dec 2006 03:16:05 +0300 (MSK)
- Subject: RE: PATCH: Move operand/address-size override prefixes before SIMD prefix
- References: <1449F58C868D8D4E9C72945771150BDFDF496D@SAUSEXMB1.amd.com>
On Wed, 6 Dec 2006, Menezes, Evandro wrote:
Perhaps you could also comment on this:
http://sourceware.org/ml/binutils/2006-11/msg00124.html
IIUC, that's not the same thing, for 0x0f is not a prefix, but part of the opcode and the prefixes (0xf3 0x66) must come before the opcode (0x0f 0x11). See chapter 1 of http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/24594.pdf.
Yes i know and now realize the mistake i made in the example byte stream -
the line should have read:
0xf3 0x66 0x0f 0x11 ..
The original question remains:
<quote>
What will it be? `movss', `movupd' #UD? Does the first prefix takes
precedence or is there some sort of built in precedence rules (i.e.
not all prefixes are equal)?
</quote>
--
vale