03.03.2013 Views

Intel® Architecture Instruction Set Extensions Programming Reference

Intel® Architecture Instruction Set Extensions Programming Reference

Intel® Architecture Instruction Set Extensions Programming Reference

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

OPCODE MAP<br />

A.2.5 Superscripts Utilized in Opcode Tables<br />

Table A-1 contains notes on particular encodings. These notes are indicated in the following opcode maps by superscripts.<br />

Gray cells indicate instruction groupings.<br />

Table A-1. Superscripts Utilized in Opcode Tables<br />

Superscript Meaning of Symbol<br />

Symbol<br />

1A Bits 5, 4, and 3 of ModR/M byte used as an opcode extension (refer to Section A.4, “Opcode <strong>Extensions</strong> For One-Byte<br />

And Two-byte Opcodes”).<br />

1B Use the 0F0B opcode (UD2 instruction) or the 0FB9H opcode when deliberately trying to generate an invalid opcode<br />

exception (#UD).<br />

1C Some instructions use the same two-byte opcode. If the instruction has variations, or the opcode represents<br />

different instructions, the ModR/M byte will be used to differentiate the instruction. For the value of the ModR/M<br />

byte needed to decode the instruction, see Table A-6.<br />

i64 The instruction is invalid or not encodable in 64-bit mode. 40 through 4F (single-byte INC and DEC) are REX prefix<br />

combinations when in 64-bit mode (use FE/FF Grp 4 and 5 for INC and DEC).<br />

o64 <strong>Instruction</strong> is only available when in 64-bit mode.<br />

d64 When in 64-bit mode, instruction defaults to 64-bit operand size and cannot encode 32-bit operand size.<br />

f64 The operand size is forced to a 64-bit operand size when in 64-bit mode (prefixes that change operand size are<br />

ignored for this instruction in 64-bit mode).<br />

v VEX form only exists. There is no legacy SSE form of the instruction. For Integer GPR instructions it means VEX<br />

prefix required.<br />

v1 VEX128 & SSE forms only exist (no VEX256), when can’t be inferred from the data size.<br />

A.3 ONE, TWO, AND THREE-BYTE OPCODE MAPS<br />

See Table A-2 through Table A-5 below. The tables are multiple page presentations. Rows and columns with<br />

sequential relationships are placed on facing pages to make look-up tasks easier. Note that table footnotes are not<br />

presented on each page. Table footnotes for each table are presented on the last page of the table.<br />

A-6 Ref. # 319433-014

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!