Misplaced Pages

The x86 instruction set refers to the set of instructions that x86-compatible microprocessors support. The instructions are usually part of an executable program, often stored as a computer file and executed on the processor.

The x86 instruction set has been extended several times, introducing wider registers and datatypes as well as new functionality.

x86 integer instructions

Below is the full 8086/8088 instruction set of Intel (81 instructions total). These instructions are also available in 32-bit mode, in which they operate on 32-bit registers (eax, ebx, etc.) and values instead of their 16-bit (ax, bx, etc.) counterparts. The updated instruction set is grouped according to architecture (i186, i286, i386, i486, i586/i686) and is referred to as (32-bit) x86 and (64-bit) x86-64 (also known as AMD64).

Original 8086/8088 instructions

This is the original instruction set. In the 'Notes' column, r means register, m means memory address and imm means immediate (i.e. a value).

if (DF==0) *(byte*)SI++ - *(byte*)ES:DI++;
else       *(byte*)SI-- - *(byte*)ES:DI--;

if (DF==0) *(word*)SI++ - *(word*)ES:DI++;
else       *(word*)SI-- - *(word*)ES:DI--;

if (DF==0) *(byte*)ES:DI++ = *(byte*)SI++;
else       *(byte*)ES:DI-- = *(byte*)SI--;

if (DF==0) *(word*)ES:DI++ = *(word*)SI++;
else       *(word*)ES:DI-- = *(word*)SI--;

Added in specific processors

Added with 80186/80188

IN AL, DX
MOV ES:, AL
INC DI ; adjust DI according to operand size and DF

MOV AL, DS:
OUT DX, AL
INC SI ; adjust SI according to operand size and DF

POP DI
POP SI
POP BP
POP AX ; no POP SP here, all it does is ADD SP, 2 (since AX will be overwritten later)
POP BX
POP DX
POP CX
POP AX

PUSH AX
PUSH CX
PUSH DX
PUSH BX
PUSH SP ; The value stored is the initial SP value
PUSH BP
PUSH SI
PUSH DI

PUSH 12h
PUSH 1200h

IMUL BX,12h
IMUL DX,1200h
IMUL CX, DX, 12h
IMUL BX, SI, 1200h
IMUL DI, word ptr , 12h
IMUL SI, word ptr , 1200h

ROL AX,3
SHR BL,3

Added with 80286

The new instructions added in 80286 add support for x86 protected mode. Some but not all of the instructions are available in real mode as well.

if (dst & 3) < (src & 3) then
   dst = (dst & 0xFFFC) | (src & 3)
   eflags.zf = 1
else
   eflags.zf = 0

1. ^ The descriptors used by the LGDT, LIDT, SGDT and SIDT instructions consist of a 2-part data structure. The first part is a 16-bit value, specifying table size in bytes minus 1. The second part is a 32-bit value (64-bit value in 64-bit mode), specifying the linear start address of the table.
   For LGDT and LIDT with a 16-bit operand size, the address is ANDed with 00FFFFFFh. On Intel (but not AMD) CPUs, the SGDT and SIDT instructions with a 16-bit operand size is – as of Intel SDM revision 079, March 2023 – documented to write a descriptor to memory with the last byte being set to 0. However, observed behavior is that bits 31:24 of the descriptor table address are written instead.
2. ^ The LGDT, LIDT, LLDT and LTR instructions are serializing on Pentium and later processors.
3. The LMSW instruction is serializing on Intel processors from Pentium onwards, but not on AMD processors.
4. On 80386 and later, the "Machine Status Word" is the same as the CR0 control register – however, the LMSW instruction can only modify the bottom 4 bits of this register and cannot clear bit 0. The inability to clear bit 0 means that LMSW can be used to enter but not leave x86 Protected Mode.
   On 80286, it is not possible to leave Protected Mode at all (neither with LMSW nor with LOADALL) without a CPU reset – on 80386 and later, it is possible to leave Protected Mode, but this requires the use of the 80386-and-later MOV to CR0 instruction.
5. If CR4.UMIP=1 is set, then the SGDT, SIDT, SLDT, SMSW and STR instructions can only run in Ring 0.
   These instructions were unprivileged on all x86 CPUs from 80286 onwards until the introduction of UMIP in 2017. This has been a significant security problem for software-based virtualization, since it enables these instructions to be used by a VM guest to detect that it is running inside a VM.
6. ^ The SMSW, SLDT and STR instructions always use an operand size of 16 bits when used with a memory argument. With a register argument on 80386 or later processors, wider destination operand sizes are available and behave as follows:
   • SMSW: Stores full CR0 in x86-64 long mode, undefined otherwise.
   • SLDT: Zero-extends 16-bit argument on Pentium Pro and later processors, undefined on earlier processors.
   • STR: Zero-extends 16-bit argument.
7. In 64-bit long mode, the ARPL instruction is not available – the 63 /r opcode has been reassigned to the 64-bit-mode-only MOVSXD instruction.
8. The ARPL instruction causes #UD in Real mode and Virtual 8086 Mode – Windows 95 and OS/2 2.x are known to make extensive use of this #UD to use the 63 opcode as a one-byte breakpoint to transition from Virtual 8086 Mode to kernel mode.
9. Bits 19:16 of this mask are documented as "undefined" on Intel CPUs. On AMD CPUs, the mask is documented as 0x00FFFF00.
10. On some Intel CPU/microcode combinations from 2019 onwards, the VERW instruction also flushes microarchitectural data buffers. This enables it to be used as part of workarounds for Microarchitectural Data Sampling security vulnerabilities.
11. ^ Undocumented, 80286 only. (A different variant of LOADALL with a different opcode and memory layout exists on 80386.)

Added with 80386

The 80386 added support for 32-bit operation to the x86 instruction set. This was done by widening the general-purpose registers to 32 bits and introducing the concepts of OperandSize and AddressSize – most instruction forms that would previously take 16-bit data arguments were given the ability to take 32-bit arguments by setting their OperandSize to 32 bits, and instructions that could take 16-bit address arguments were given the ability to take 32-bit address arguments by setting their AddressSize to 32 bits. (Instruction forms that work on 8-bit data continue to be 8-bit regardless of OperandSize. Using a data size of 16 bits will cause only the bottom 16 bits of the 32-bit general-purpose registers to be modified – the top 16 bits are left unchanged.)

The default OperandSize and AddressSize to use for each instruction is given by the D bit of the segment descriptor of the current code segment - D=0 makes both 16-bit, D=1 makes both 32-bit. Additionally, they can be overridden on a per-instruction basis with two new instruction prefixes that were introduced in the 80386:

• 66h: OperandSize override. Will change OperandSize from 16-bit to 32-bit if CS.D=0, or from 32-bit to 16-bit if CS.D=1.
• 67h: AddressSize override. Will change AddressSize from 16-bit to 32-bit if CS.D=0, or from 32-bit to 16-bit if CS.D=1.

The 80386 also introduced the two new segment registers FS and GS as well as the x86 control, debug and test registers.

The new instructions introduced in the 80386 can broadly be subdivided into two classes:

• Pre-existing opcodes that needed new mnemonics for their 32-bit OperandSize variants (e.g. CWDE, LODSD)
• New opcodes that introduced new functionality (e.g. SHLD, SETcc)

For instruction forms where the operand size can be inferred from the instruction's arguments (e.g. ADD EAX,EBX can be inferred to have a 32-bit OperandSize due to its use of EAX as an argument), new instruction mnemonics are not needed and not provided.

temp1 := DS:
temp2 := ES:
CMP temp1, temp2 /* 32-bit compare and set EFLAGS */

temp1 := ES:
CMP EAX, temp1 /* 32-bit compare and set EFLAGS */

1. For the 32-bit string instructions, the ±± notation is used to indicate that the indicated register is post-decremented by 4 if EFLAGS.DF=1 and post-incremented by 4 otherwise.
   For the operands where the DS segment is indicated, the DS segment can be overridden by a segment-override prefix – where the ES segment is indicated, the segment is always ES and cannot be overridden.
   The choice of whether to use the 16-bit SI/DI registers or the 32-bit ESI/EDI registers as the address registers to use is made by AddressSize, overridable with the 67 prefix.
2. The 32-bit string instructions accept repeat-prefixes in the same way as older 8/16-bit string instructions.
   For LODSD, STOSD, MOVSD, INSD and OUTSD, the REP prefix (F3) will repeat the instruction the number of times specified in rCX (CX or ECX, decided by AddressSize), decrementing rCX for each iteration (with rCX=0 resulting in no-op and proceeding to the next instruction).
   For CMPSD and SCASD, the REPE (F3) and REPNE (F2) prefixes are available, which will repeat the instruction, decrementing rCX for each iteration, but only as long as the flag condition (ZF=1 for REPE, ZF=0 for REPNE) holds true AND rCX ≠ 0.
3. For the INSB/W/D instructions, the memory access rights for the ES: memory address might not be checked until after the port access has been performed – if this check fails (e.g. page fault or other memory exception), then the data item read from the port is lost. As such, it is not recommended to use this instruction to access an I/O port that performs any kind of side effect upon read.
4. I/O port access is only allowed when CPL≤IOPL or the I/O port permission bitmap bits for the port to access are all set to 0.
5. The CWDE instruction differs from the older CWD instruction in that CWD would sign-extend the 16-bit value in AX into a 32-bit value in the DX:AX register pair.
6. For the E3 opcode (JCXZ/JECXZ), the choice of whether the instruction will use CX or ECX for its comparison (and consequently which mnemonic to use) is based on the AddressSize, not OperandSize. (OperandSize instead controls whether the jump destination should be truncated to 16 bits or not).
   This also applies to the loop instructions LOOP,LOOPE,LOOPNE (opcodes E0,E1,E2), however, unlike JCXZ/JECXZ, these instructions have not been given new mnemonics for their ECX-using variants.
7. For PUSHA(D), the value of SP/ESP pushed onto the stack is the value it had just before the PUSHA(D) instruction started executing.
8. For POPA/POPAD, the stack item corresponding to SP/ESP is popped off the stack (performing a memory read), but not placed into SP/ESP.
9. The PUSHFD and POPFD instructions will cause a #GP exception if executed in virtual 8086 mode if IOPL is not 3.
   The PUSHF, POPF, IRET and IRETD instructions will cause a #GP exception if executed in Virtual-8086 mode if IOPL is not 3 and VME is not enabled.
10. If IRETD is used to return from kernel mode to user mode (which will entail a CPL change) and the user-mode stack segment indicated by SS is a 16-bit segment, then the IRETD instruction will only restore the low 16 bits of the stack pointer (ESP/RSP), with the remaining bits keeping whatever value they had in kernel code before the IRETD. This has necessitated complex workarounds on both Linux ("ESPFIX") and Windows. This issue also affects the later 64-bit IRETQ instruction.

1. ^ For the BT, BTS, BTR and BTC instructions:
   • If the first argument to the instruction is a register operand and/or the second argument is an immediate, then the bit-index in the second argument is taken modulo operand size (16/32/64, in effect using only the bottom 4, 5 or 6 bits of the index.)
   • If the first argument is a memory operand and the second argument is a register operand, then the bit-index in the second argument is used in full – it is interpreted as a signed bit-index that is used to offset the memory address to use for the bit test.
2. ^ The BTS, BTC and BTR instructions accept the LOCK (F0) prefix when used with a memory argument – this results in the instruction executing atomically.
3. If the F3 prefix is used with the 0F BC /r opcode, then the instruction will execute as TZCNT on systems that support the BMI1 extension. TZCNT differs from BSF in that TZCNT but not BSR is defined to return operand size if the source operand is zero – for other source operand values, they produce the same result (except for flags).
4. ^ BSF and BSR set the EFLAGS.ZF flag to 1 if the source argument was all-0s and 0 otherwise.
   If the source argument was all-0s, then the destination register is documented as being left unchanged on AMD processors, but set to an undefined value on Intel processors.
5. If the F3 prefix is used with the 0F BD /r opcode, then the instruction will execute as LZCNT on systems that support the ABM or LZCNT extensions. LZCNT produces a different result from BSR for most input values.
6. ^ For SHLD and SHRD, the shift-amount is masked – the bottom 5 bits are used for 16/32-bit operand size and 6 bits for 64-bit operand size.
   SHLD and SHRD with 16-bit arguments and a shift-amount greater than 16 produce undefined results. (Actual results differ between different Intel CPUs, with at least three different behaviors known.)
7. ^ The condition codes supported for the SETcc and Jcc near instructions (opcodes 0F 9x /0 and 0F 8x respectively, with the x nibble specifying the condition) are:

   x	cc	Condition (EFLAGS)
   0	O	OF=1: "Overflow"
   1	NO	OF=0: "Not Overflow"
   2	C,B,NAE	CF=1: "Carry", "Below", "Not Above or Equal"
   3	NC,NB,AE	CF=0: "Not Carry", "Not Below", "Above or Equal"
   4	Z,E	ZF=1: "Zero", "Equal"
   5	NZ,NE	ZF=0: "Not Zero", "Not Equal"
   6	NA,BE	(CF=1 or ZF=1): "Not Above", "Below or Equal"
   7	A,NBE	(CF=0 and ZF=0): "Above", "Not Below or Equal"
   8	S	SF=1: "Sign"
   9	NS	SF=0: "Not Sign"
   A	P,PE	PF=1: "Parity", "Parity Even"
   B	NP,PO	PF=0: "Not Parity", "Parity Odd"
   C	L,NGE	SF≠OF: "Less", "Not Greater Or Equal"
   D	NL,GE	SF=OF: "Not Less", "Greater Or Equal"
   E	LE,NG	(ZF=1 or SF≠OF): "Less or Equal", "Not Greater"
   F	NLE,G	(ZF=0 and SF=OF): "Not Less or Equal", "Greater"

8. For SETcc, while the opcode is commonly specified as /0 – implying that bits 5:3 of the instruction's ModR/M byte should be 000 – modern x86 processors (Pentium and later) ignore bits 5:3 and will execute the instruction as SETcc regardless of the contents of these bits.
9. For LFS, LGS and LSS, the size of the offset part of the far pointer is given by operand size – the size of the segment part is always 16 bits. In 64-bit mode, using the REX.W prefix with these instructions will cause them to load a far pointer with a 64-bit offset on Intel but not AMD processors.
10. ^ For MOV to/from the CRx, DRx and TRx registers, the reg part of the ModR/M byte is used to indicate CRx/DRx/TRx register and r/m part the general-register. Uniquely for the MOV CRx/DRx/TRx opcodes, the top two bits of the ModR/M byte is ignored – these opcodes are decoded and executed as if the top two bits of the ModR/M byte are 11b.
11. ^ For moves to/from the CRx and DRx registers, the operand size is always 64 bits in 64-bit mode and 32 bits otherwise.
12. On processors that support global pages (Pentium and later), global page table entries will not be flushed by a MOV to CR3 − instead, these entries can be flushed by toggling the CR4.PGE bit.
    On processors that support PCIDs, writing to CR3 while PCIDs are enabled will only flush TLB entries belonging to the PCID specified in bits 11:0 of the value written to CR3 (this flush can be suppressed by setting bit 63 of the written value to 1). Flushing pages belonging to other PCIDs can instead be done by toggling the CR4.PGE bit, clearing the CR4.PCIDE bit, or using the INVPCID instruction.
13. On processors prior to Pentium, moves to CR0 would not serialize the instruction stream – in part for this reason, it is usually required to perform a far jump immediately after a MOV to CR0 if such a MOV is used to enable/disable protected mode and/or memory paging.
    MOV to CR2 is architecturally listed as serializing, but has been reported to be non-serializing on at least some Intel Core-i7 processors.
    MOV to CR8 (introduced with x86-64) is serializing on AMD but not Intel processors.
14. ^ The MOV TRx instructions were discontinued from Pentium onwards.
15. The INT1/ICEBP (F1) instruction is present on all known Intel x86 processors from the 80386 onwards, but only fully documented for Intel processors from the May 2018 release of the Intel SDM (rev 067) onwards. Before this release, mention of the instruction in Intel material was sporadic, e.g. AP-526 rev 001.
    For AMD processors, the instruction has been documented since 2002.
16. The operation of the F1(ICEBP) opcode differs from the operation of the regular software interrupt opcode CD 01 in several ways:
    In protected mode, CD 01 will check CPL against the interrupt descriptor's DPL field as an access-rights check, while F1 will not.
    • In virtual-8086 mode, CD 01 will also check CPL against IOPL as an access-rights check, while F1 will not.
    • In virtual-8086 mode with VME enabled, interrupt redirection is supported for CD 01 but not F1.
17. The UMOV instruction is present on 386 and 486 processors only.
18. ^ The XBTS and IBTS instructions were discontinued with the B1 stepping of 80386.
    They have been used by software mainly for detection of the buggy B0 stepping of the 80386. Microsoft Windows (v2.01 and later) will attempt to run the XBTS instruction as part of its CPU detection if CPUID is not present, and will refuse to boot if XBTS is found to be working.
19. ^ For XBTS and IBTS, the r/m argument represents the data to extract/insert a bitfield from/to, the reg argument the bitfield to be inserted/extracted, AX/EAX a bit-offset and CL a bitfield length.
20. Undocumented, 80386 only.

Added with 80486

r =   (r << 24)
    | ((r << 8) & 0x00FF0000)
    | ((r >> 8) & 0x0000FF00)
    | (r >> 24);

1. Using BSWAP with 16-bit registers is not disallowed per se (it will execute without producing an #UD or other exceptions) but is documented to produce undefined results – it is reported to produce various different results on 486, 586, and Bochs/QEMU.
2. ^ On Intel 80486 stepping A, the CMPXCHG instruction uses a different encoding - 0F A6 /r for 8-bit variant, 0F A7 /r for 16/32-bit variant. The 0F B0/B1 encodings are used on 80486 stepping B and later.
3. The CMPXCHG instruction sets EFLAGS in the same way as a CMP instruction that uses the accumulator (AL/AX/EAX/RAX) as its first argument would do.
4. INVLPG executes as no-operation if the m8 argument is invalid (e.g. unmapped page or non-canonical address).
   INVLPG can be used to invalidate TLB entries for individual global pages.
5. ^ The INVD and WBINVD instructions will invalidate all cache lines in the CPU's L1 caches. It is implementation-defined whether they will invalidate L2/L3 caches as well.
   These instructions are serializing – on some processors, they may block interrupts until completion as well.
6. Under Intel VT-x virtualization, the INVD instruction will cause a mandatory #VMEXIT. Also, on processors that support Intel SGX, if the PRM (Processor Reserved Memory) has been set up by using the PRMRRs (PRM range registers), then the INVD instruction is not permitted and will cause a #GP(0) exception.
7. If the F3 prefix is used with the 0F 09 opcode, then the instruction will execute as WBNOINVD on processors that support the WBNOINVD extension – this will not invalidate the cache.

Added in P5/P6-class processors

Integer/system instructions that were not present in the basic 80486 instruction set, but were added in various x86 processors prior to the introduction of SSE. (Discontinued instructions are not included.)

1. On Intel and AMD CPUs, the WRMSR instruction is also used to update the CPU microcode. This is done by writing the virtual address of the new microcode to upload to MSR 79h on Intel CPUs and MSR C001_0020h on AMD CPUs.
2. Writes to the following MSRs are not serializing:

   Number	Name
   48h	SPEC_CTRL
   49h	PRED_CMD
   10Bh	FLUSH_CMD
   122h	TSX_CTRL
   6E0h	TSC_DEADLINE
   6E1h	PKRS
   774h	HWP_REQUEST (non-serializing only if the FAST_IA32_­HWP_REQUEST bit it set)
   802h to 83Fh	(x2APIC MSRs)
   1B01h	UARCH_MISC_CTL
   C001_0100h	FS_BASE (non-serializing on AMD Zen 4 and later)
   C001_0101h	GS_BASE (Zen 4 and later)
   C001_0102h	KernelGSbase (Zen 4 and later)
   C001_011Bh	Doorbell Register (AMD-specific)

3. System Management Mode and the RSM instruction were made available on non-SL variants of the Intel 486 only after the initial release of the Intel Pentium in 1993.
4. On some older 32-bit processors, executing CPUID with a leaf index (EAX) greater than 0 may leave EBX and ECX unmodified, keeping their old values. For this reason, it is recommended to zero out EBX and ECX before executing CPUID.
   Processors noted to exhibit this behavior include Cyrix MII and IDT WinChip 2.
   
   In 64-bit mode, CPUID will set the top 32 bits of RAX, RBX, RCX and RDX to zero.
5. On some Intel processors starting from Ivy Bridge, there exists MSRs that can be used to restrict CPUID to ring 0. Such MSRs are documented for at least Ivy Bridge and Denverton.
   The ability to restrict CPUID to ring 0 also exists on AMD processors supporting the "CpuidUserDis" feature (Zen 4 "Raphael" and later).
6. ^ CPUID is also available on some Intel and AMD 486 processor variants that were released after the initial release of the Intel Pentium.
7. On the Cyrix 5x86 and 6x86 CPUs, CPUID is not enabled by default and must be enabled through a Cyrix configuration register.
8. On NexGen CPUs, CPUID is only supported with some system BIOSes. On some NexGen CPUs that do support CPUID, EFLAGS.ID is not supported but EFLAGS.AC is, complicating CPU detection.
9. Unlike the older CMPXCHG instruction, the CMPXCHG8B instruction does not modify any EFLAGS bits other than ZF.
10. LOCK CMPXCHG8B with a register operand (which is an invalid encoding) will, on some Intel Pentium CPUs, cause a hang rather than the expected #UD exception - this is known as the Pentium F00F bug.
11. ^ On IDT WinChip, Transmeta Crusoe and Rise mP6 processors, the CMPXCHG8B instruction is always supported, however its CPUID bit may be missing. This is a workaround for a bug in Windows NT.
12. ^ The RDTSC and RDPMC instructions are not ordered with respect to other instructions, and may sample their respective counters before earlier instructions are executed or after later instructions have executed. Invocations of RDPMC (but not RDTSC) may be reordered relative to each other even for reads of the same counter.
    In order to impose ordering with respect to other instructions, LFENCE or serializing instructions (e.g. CPUID) are needed.
13. Fixed-rate TSC was introduced in two stages:

    Constant TSC

    TSC running at a fixed rate as long as the processor core is not in a deep-sleep (C2 or deeper) mode, but not synchronized between CPU cores. Introduced in Intel Prescott, Yonah and Bonnell. Also present in all Transmeta and VIA Nano CPUs. Does not have a CPUID bit.

    Invariant TSC

    TSC running at a fixed rate, and remaining synchronized between CPU cores in all P-,C- and T-states (but not necessarily S-states).
    Present in AMD K10 and later; Intel Nehalem/Saltwell and later; Zhaoxin WuDaoKou and later. Indicated with a CPUID bit (leaf 8000_0007:EDX).

14. RDTSC can be run outside Ring 0 only if CR4.TSD=0.
    On Intel Pentium and AMD K5, RDTSC cannot be run in Virtual-8086 mode. Later processors removed this restriction.
15. RDPMC can be run outside Ring 0 only if CR4.PCE=1.
16. The RDPMC instruction is not present in VIA processors prior to the Nano.
17. The condition codes supported for CMOVcc instruction (opcode 0F 4x /r, with the x nibble specifying the condition) are:

    x	cc	Condition (EFLAGS)
    0	O	OF=1: "Overflow"
    1	NO	OF=0: "Not Overflow"
    2	C,B,NAE	CF=1: "Carry", "Below", "Not Above or Equal"
    3	NC,NB,AE	CF=0: "Not Carry", "Not Below", "Above or Equal"
    4	Z,E	ZF=1: "Zero", "Equal"
    5	NZ,NE	ZF=0: "Not Zero", "Not Equal"
    6	NA,BE	(CF=1 or ZF=1): "Not Above", "Below or Equal"
    7	A,NBE	(CF=0 and ZF=0): "Above", "Not Below or Equal"
    8	S	SF=1: "Sign"
    9	NS	SF=0: "Not Sign"
    A	P,PE	PF=1: "Parity", "Parity Even"
    B	NP,PO	PF=0: "Not Parity", "Parity Odd"
    C	L,NGE	SF≠OF: "Less", "Not Greater Or Equal"
    D	NL,GE	SF=OF: "Not Less", "Greater Or Equal"
    E	LE,NG	(ZF=1 or SF≠OF): "Less or Equal", "Not Greater"
    F	NLE,G	(ZF=0 and SF=OF): "Not Less or Equal", "Greater"

18. In 64-bit mode, CMOVcc with a 32-bit operand size will clear the upper 32 bits of the destination register even if the condition is false.
    For CMOVcc with a memory source operand, the CPU will always read the operand from memory – potentially causing memory exceptions and cache line-fills – even if the condition for the move is not satisfied. (The Intel APX extension defines a set of new EVEX-encoded variants of CMOVcc that will suppress memory exceptions if the condition is false.)
19. On pre-Nehemiah VIA C3 variants ("Samuel"/"Ezra"), the reg,reg but not reg, forms of the CMOVcc instructions have been reported to be present as undocumented instructions.
20. Intel's recommended byte encodings for multi-byte NOPs of lengths 2 to 9 bytes in 32/64-bit mode are (in hex):

    Length	Byte Sequence
    2	66 90
    3	0F 1F 00
    4	0F 1F 40 00
    5	0F 1F 44 00 00
    6	66 0F 1F 44 00 00
    7	0F 1F 80 00 00 00 00
    8	0F 1F 84 00 00 00 00 00
    9	66 0F 1F 84 00 00 00 00 00

    For cases where there is a need to use more than 9 bytes of NOP padding, it is recommended to use multiple NOPs.

21. Unlike other instructions added in Pentium Pro, long NOP does not have a CPUID feature bit.
22. 0F 1F /0 as long-NOP was introduced in the Pentium Pro, but remained undocumented until 2006. The whole 0F 18..1F opcode range was NOP in Pentium Pro. However, except for 0F 1F /0, Intel does not guarantee that these opcodes will remain NOP in future processors, and have indeed assigned some of these opcodes to other instructions in at least some processors.
23. Documented for AMD x86-64 since 2002.
24. While the 0F 0B opcode was officially reserved as an invalid opcode from Pentium onwards, it only got assigned the mnemonic UD2 from Pentium Pro onwards.
25. ^ GNU Binutils have used the UD2A and UD2B mnemonics for the 0F 0B and 0F B9 opcodes since version 2.7.
    Neither UD2A nor UD2B originally took any arguments - UD2B was later modified to accept a ModR/M byte, in Binutils version 2.30.
26. The UD2 (0F 0B) instruction will additionally stop subsequent bytes from being decoded as instructions, even speculatively. For this reason, if an indirect branch instruction is followed by something that is not code, it is recommended to place an UD2 instruction after the indirect branch.
27. ^ The UD0/1/2 opcodes - 0F 0B, 0F B9 and 0F FF - will cause an #UD exception on all x86 processors from the 80186 onwards (except NEC V-series processors), but did not get explicitly reserved for this purpose until P5-class processors.
28. While the 0F B9 opcode was officially reserved as an invalid opcode from Pentium onwards, it only got assigned its mnemonic UD1 much later – AMD APM started listing UD1 in its opcode maps from rev 3.17 onwards, while Intel SDM started listing it from rev 061 onwards.
29. ^ For both the 0F B9 and 0F FF opcodes, different x86 implementations are known to differ regarding whether the opcodes accept a ModR/M byte.
30. For the 0F FF opcode, the OIO mnemonic was introduced by Cyrix, while the UD0 menmonic (without arguments) was introduced by AMD and Intel at the same time as the UD1 mnemonic for 0F B9. Later Intel (but not AMD) documentation modified its description of UD0 to add a ModR/M byte and take two arguments.
31. On K6, the SYSCALL/SYSRET instructions were available on Model 7 (250nm "Little Foot") and later, not on the earlier Model 6.
32. SYSCALL and SYSRET were made an integral part of x86-64 – as a result, the instructions are available in 64-bit mode on all x86-64 processors from AMD, Intel, VIA and Zhaoxin.
    Outside 64-bit mode, the instructions are available on AMD processors only.
33. The exact semantics of SYSRET differs slightly between AMD and Intel processors: non-canonical return addresses cause a #GP exception to be thrown in Ring 3 on AMD CPUs but Ring 0 on Intel CPUs. This has been known to cause security issues.
34. ^ For the SYSRET and SYSEXIT instructions under x86-64, it is necessary to add the REX.W prefix for variants that will return to 64-bit user-mode code.
    Encodings of these instructions without the REX.W prefix are used to return to 32-bit user-mode code. (Neither of these instructions can be used to return to 16-bit user-mode code.)
35. ^ The SYSRET, SYSENTER and SYSEXIT instructions are unavailable in Real mode. (SYSENTER is, however, available in Virtual 8086 mode.)
36. The CPUID flags that indicate support for SYSENTER/SYSEXIT are set on the Pentium Pro, even though the processor does not officially support these instructions.
    Third party testing indicates that the opcodes are present on the Pentium Pro but too buggy to be usable.
37. On AMD CPUs, the SYSENTER and SYSEXIT instructions are not available in x86-64 long mode (#UD).
38. On Transmeta CPUs, the SYSENTER and SYSEXIT instructions are only available with version 4.2 or higher of the Transmeta Code Morphing software.
39. On Nehemiah, SYSENTER and SYSEXIT are available only on stepping 8 and later.

Added as instruction set extensions

Added with x86-64

These instructions can only be encoded in 64 bit mode. They fall in four groups:

• original instructions that reuse existing opcodes for a different purpose (MOVSXD replacing ARPL)
• original instructions with new opcodes (SWAPGS)
• existing instructions extended to a 64 bit address size (JRCXZ)
• existing instructions extended to a 64 bit operand size (remaining instructions)

Most instructions with a 64 bit operand size encode this using a REX.W prefix; in the absence of the REX.W prefix, the corresponding instruction with 32 bit operand size is encoded. This mechanism also applies to most other instructions with 32 bit operand size. These are not listed here as they do not gain a new mnemonic in Intel syntax when used with a 64 bit operand size.

1. The memory operand to CMPXCHG16B must be 16-byte aligned.
2. The CMPXCHG16B instruction was absent from a few of the earliest Intel/AMD x86-64 processors. On Intel processors, the instruction was missing from Xeon "Nocona" stepping D, but added in stepping E. On AMD K8 family processors, it was added in stepping F, at the same time as DDR2 support was introduced.
   For this reason, CMPXCHG16B has its own CPUID flag, separate from the rest of x86-64.
3. Encodings of MOVSXD without REX.W prefix are permitted but discouraged – such encodings behave identically to 16/32-bit MOV (8B /r).

Bit manipulation extensions

Bit manipulation instructions. For all of the VEX-encoded instructions defined by BMI1 and BMI2, the operand size may be 32 or 64 bits, controlled by the VEX.W bit – none of these instructions are available in 16-bit variants.

mask = (1 << rb) - 1
ra = (r/m >> rb) AND mask

ra=0; k=0; mask=r/m
for i=0 to opsize-1 do
   if (mask == 1) then
       ra=rb; k=k+1

ra=0; k=0; mask=r/m
for i=0 to opsize-1 do
   if (mask == 1) then
       ra=rb; k=k+1

1. On AMD CPUs, the "ABM" extension provides both POPCNT and LZCNT. On Intel CPUs, however, the CPUID bit for "ABM" is only documented to indicate the presence of the LZCNT instruction and is listed as "LZCNT", while POPCNT has its own separate CPUID feature bit.
   However, all known processors that implement the "ABM"/"LZCNT" extensions also implement POPCNT and set the CPUID feature bit for POPCNT, so the distinction is theoretical only.
   (The converse is not true – there exist processors that support POPCNT but not ABM, such as Intel Nehalem and VIA Nano 3000.)
2. The LZCNT instruction will execute as BSR on systems that do not support the LZCNT or ABM extensions. BSR computes the index of the highest set bit in the source operand, producing a different result from LZCNT for most input values.
3. The TZCNT instruction will execute as BSF on systems that do not support the BMI1 extension. BSF produces the same result as TZCNT for all input operand values except zero – for which TZCNT returns input operand size, but BSF produces undefined behavior (leaves destination unmodified on most modern CPUs).
4. For BEXTR, the start position and length are not masked and can take values from 0 to 255. If the selected bits extend beyond the end of the r/m argument (which has the usual 32/64-bit operand size), then the excess bits are read out as 0.
5. On AMD processors before Zen 3, the PEXT and PDEP instructions are quite slow and exhibit data-dependent timing due to the use of a microcoded implementation (about 18 to 300 cycles, depending on the number of bits set in the mask argument). As a result, it is often faster to use other instruction sequences on these processors.

Added with Intel TSX

Added with Intel CET

Intel CET (Control-Flow Enforcement Technology) adds two distinct features to help protect against security exploits such as return-oriented programming: a shadow stack (CET_SS), and indirect branch tracking (CET_IBT).

1. ^ The RDSSPD and RDSSPQ instructions act as NOPs on processors where shadow stacks are disabled or CET is not supported.
2. ^ ENDBR32 and ENDBR64 act as NOPs on processors that don't support CET_IBT or where IBT is disabled.
3. This prefix has the same encoding as the DS: segment override prefix – as of April 2022, Intel documentation does not appear to specify whether this prefix also retains its old segment-override function when used as a no-track prefix, nor does it provide an official mnemonic for this prefix. (GNU binutils use "notrack")

Added with XSAVE

The XSAVE instruction set extensions are designed to save/restore CPU extended state (typically for the purpose of context switching) in a manner that can be extended to cover new instruction set extensions without the OS context-switching code needing to understand the specifics of the new extensions. This is done by defining a series of state-components, each with a size and offset within a given save area, and each corresponding to a subset of the state needed for one CPU extension or another. The EAX=0Dh CPUID leaf is used to provide information about which state-components the CPU supports and what their sizes/offsets are, so that the OS can reserve the proper amount of space and set the associated enable-bits.

1. Under Intel APX, the XSAVE* and XRSTOR* instructions cannot be encoded with the REX2 prefix.
2. XSAVE was added in steppings E0/R0 of Penryn and is not available in earlier steppings.
3. On some processors (starting with Skylake, Goldmont and Zen 1), executing XGETBV with ECX=1 is permitted – this will not return XCR1 (no such register exists) but instead return XCR0 bitwise-ANDed with the current value of the "XINUSE" state-component bitmap (a bitmap of XSAVE state-components that are not known to be in their initial state).
   The presence of this functionality of XGETBV is indicated by CPUID.(EAX=0Dh,ECX=1):EAX.
4. The XSETBV instruction will cause a mandatory #VMEXIT if executed under Intel VT-x virtualization.

Added with other cross-vendor extensions

1. ^ AMD Athlon processors prior to the Athlon XP did not support full SSE, but did introduce the non-SIMD instructions of SSE as part of "MMX Extensions". These extensions (without full SSE) are also present on Geode GX2 and later Geode processors.
2. ^ All of the PREFETCH* instructions are hint instructions with effects only on performance, not program semantics. Providing an invalid address (e.g. address of an unmapped page or a non-canonical address) will cause the instruction to act as a NOP without any exceptions generated.
3. ^ For the SFENCE, LFENCE and MFENCE instructions, the bottom 3 bits of the ModR/M byte are ignored, and any value of x in the range 0..7 will result in a valid instruction.
4. The SFENCE instruction ensures that all memory stores after the SFENCE instruction are made globally observable after all memory stores before the SFENCE. This imposes ordering on stores that can otherwise be reordered, such as non-temporal stores and stores to WC (Write-Combining) memory regions.
   On Intel CPUs, as well as AMD CPUs from Zen1 onwards (but not older AMD CPUs), SFENCE also acts as a reordering barrier on cache flushes/writebacks performed with the CLFLUSH, CLFLUSHOPT and CLWB instructions. (Older AMD CPUs require MFENCE to order CLFLUSH.)
   SFENCE is not ordered with respect to LFENCE, and an SFENCE+LFENCE sequence is not sufficient to prevent a load from being reordered past a previous store. To prevent such reordering, it is necessary to execute an MFENCE, LOCK or a serializing instruction.
5. The LFENCE instruction ensures that all memory loads after the LFENCE instruction are made globally observable after all memory loads before the LFENCE.
   On all Intel CPUs that support SSE2, the LFENCE instruction provides a stronger ordering guarantee: it is dispatch-serializing, meaning that instructions after the LFENCE instruction are allowed to start executing only after all instructions before it have retired (which will ensure that all preceding loads but not necessarily stores have completed). The effect of dispatch-serialization is that LFENCE also acts as a speculation barrier and a reordering barrier for accesses to non-memory resources such as performance counters (accessed through e.g. RDTSC or RDPMC) and x2apic MSRs.
   On AMD CPUs, LFENCE is not necessarily dispatch-serializing by default – however, on all AMD CPUs that support any form of non-dispatch-serializing LFENCE, it can be made dispatch-serializing by setting bit 1 of MSR C001_1029.
6. The MFENCE instruction ensures that all memory loads, stores and cacheline-flushes after the MFENCE instruction are made globally observable after all memory loads, stores and cacheline-flushes before the MFENCE.
   On Intel CPUs, MFENCE is not dispatch-serializing, and therefore cannot be used on its own to enforce ordering on accesses to non-memory resources such as performance counters and x2apic MSRs. MFENCE is still ordered with respect to LFENCE, so if there is a need to enforce ordering between memory stores and subsequent non-memory accesses, then such an ordering can be obtained by issuing an MFENCE followed by an LFENCE.
   On AMD CPUs, MFENCE is serializing.
7. The operation of the PAUSE instruction in 64-bit mode is, unlike NOP, unaffected by the presence of the REX.R prefix. Neither NOP nor PAUSE are affected by the other bits of the REX prefix. A few examples of how opcode 90 interacts with various prefixes in 64-bit mode are:
   • 90 is NOP
   • 41 90 is XCHG R8D,EAX
   • 4E 90 is NOP
   • 49 90 is XCHG R8,RAX
   • F3 90 is PAUSE
   • F3 41 90 is PAUSE
   • F3 4F 90 is PAUSE
8. The actual length of the pause performed by the PAUSE instruction is implementation-dependent.
   On systems without SSE2, PAUSE will execute as NOP.
9. Under VT-x or AMD-V virtualization, executing PAUSE many times in a short time interval may cause a #VMEXIT. The number of PAUSE executions and interval length that can trigger #VMEXIT are platform-specific.
10. While the CLFLUSH instruction was introduced together with SSE2, it has its own CPUID flag and may be present on processors not otherwise implementing SSE2 and/or absent from processors that otherwise implement SSE2. (E.g. AMD Geode LX supports CLFLUSH but not SSE2.)
11. While the MONITOR and MWAIT instructions were introduced at the same time as SSE3, they have their own CPUID flag that needs to be checked separately from the SSE3 CPUID flag (e.g. Athlon 64 X2 and VIA C7 supported SSE3 but not MONITOR.)
12. ^ For the MONITOR and MWAIT instructions, older Intel documentation lists instruction mnemonics with explicit operands (MONITOR EAX,ECX,EDX and MWAIT EAX,ECX), while newer documentation omits these operands. Assemblers/disassemblers may support one or both of these variants.
13. For MONITOR, the DS: segment can be overridden with a segment prefix.
    The memory area that will be monitored will be not just the single byte specified by DS:rAX, but a linear memory region containing the byte – the size and alignment of this memory region is implementation-dependent and can be queried through CPUID.
    The memory location to monitor should have memory type WB (write-back cacheable), or else monitoring may fail.
14. As of April 2024, no extensions or hints have been defined for the MONITOR instruction. As such, the instruction requires ECX=0 and ignores EDX.
15. On some processors, such as Intel Xeon Phi x200 and AMD K10 and later, there exist documented MSRs that can be used to enable MONITOR and MWAIT to run in Ring 3.
16. The wait performed by MWAITmay be ended by system events other than a memory write (e.g. cacheline evictions, interrupts) – the exact set of events that can cause the wait to end is implementation-specific.
    Regardless of whether the wait was ended by a memory write or some other event, monitoring will have ended and it will be necessary to set up monitoring again with MONITOR before using MWAIT to wait for memory writes again.
17. The extension flags available for MWAIT in the ECX register are:

    Bits	MWAIT Extension
    0	Treat interrupts as break events, even when masked (EFLAGS.IF=0). (Available on all non-NetBurst implementations of MWAIT.)
    1	Timed MWAIT: end the wait when the TSC reaches or exceeds the value in EDX:EBX. (Undocumented, reportedly present in Intel Skylake and later Intel processors)
    2	Monitorless MWAIT
    31:3	Not used, must be set to zero.

18. The hint flags available for MWAIT in the EAX register are:

    Bits	MWAIT Hint
    3:0	Sub-state within a C-state (see bits 7:4) (Intel processors only)
    7:4	Target CPU power C-state during wait, minus 1. (E.g. 0000b for C1, 0001b for C2, 1111b for C0)
    31:8	Not used.

    The C-states are processor-specific power states, which do not necessarily correspond 1:1 to ACPI C-states.

19. For the GETSEC instruction, the REX.W prefix enables 64-bit addresses for the EXITAC leaf function only - REX prefixes are otherwise permitted but ignored for the instruction.
20. The leaf functions defined for GETSEC (selected by EAX) are:

    EAX	Function
    0 (CAPABILITIES)	Report SMX capabilities
    2 (ENTERACCES)	Enter execution of authenticated code module
    3 (EXITAC)	Exit execution of authenticated code module
    4 (SENTER)	Enter measured environment
    5 (SEXIT)	Exit measured environment
    6 (PARAMETERS)	Report SMX parameters
    7 (SMCTRL)	SMX Mode Control
    8 (WAKEUP)	Wake up sleeping processors in measured environment

    Any unsupported value in EAX causes an #UD exception.

21. For GETSEC, most leaf functions are restricted to Ring 0, but the CAPABILITIES (EAX=0) and PARAMETERS (EAX=6) leaf functions are available in Ring 3.
22. ^ The "core ID" value read by RDTSCP and RDPID is actually the TSC_AUX MSR (MSR C000_0103h). Whether this value actually corresponds to a processor ID is a matter of operating system convention.
23. Unlike the older RDTSC instruction, RDTSCP will delay the TSC read until all previous instructions have retired, guaranteeing ordering with respect to preceding memory loads (but not stores). RDTSCP is not ordered with respect to subsequent instructions, though.
24. RDTSCP can be run outside Ring 0 only if CR4.TSD=0.
25. Support for RDTSCP was added in stepping F of the AMD K8, and is not available on earlier steppings.
26. While the POPCNT instruction was introduced at the same time as SSE4.2, it is not considered to be a part of SSE4.2, but instead a separate extension with its own CPUID flag.
    On AMD processors, it is considered to be a part of the ABM extension, but still has its own CPUID flag.
27. The invalidation types defined for INVPCID (selected by register argument) are:

    Value	Function
    0	Invalidate TLB entries matching PCID and virtual memory address in descriptor, excluding global entries
    1	Invalidate TLB entries matching PCID in descriptor, excluding global entries
    2	Invalidate all TLB entries, including global entries
    3	Invalidate all TLB entries, excluding global entries

    Any unsupported value in the register argument causes a #GP exception.

28. Unlike the older INVLPG instruction, INVPCID will cause a #GP exception if the provided memory address is non-canonical. This discrepancy has been known to cause security issues.
29. The PREFETCH and PREFETCHW instructions are mandatory parts of the 3DNow! instruction set extension, but are also available as a standalone extension on systems that do not support 3DNow!
30. The opcodes for PREFETCH and PREFETCHW (0F 0D /r) execute as NOPs on Intel CPUs from Cedar Mill (65nm Pentium 4) onwards, with PREFETCHW gaining prefetch functionality from Broadwell onwards.
31. The PREFETCH (0F 0D /0) instruction is a 3DNow! instruction, present on all processors with 3DNow! but not necessarily on processors with the PREFETCHW extension.
    On AMD CPUs with PREFETCHW, opcode 0F 0D /0 as well as opcodes 0F 0D /2../7 are all documented to be performing prefetch.
    On Intel processors with PREFETCHW, these opcodes are documented as performing reserved-NOPs (except 0F 0D /2 being PREFETCHWT1 m8 on Xeon Phi only) – third party testing indicates that some or all of these opcodes may be performing prefetch on at least some Intel Core CPUs.
32. ^ The SMAP, PKU and RDPID instruction set extensions are supported on stepping 2 and later of Zhaoxin LuJiaZui, but not on earlier steppings.
33. Unlike the older RDTSCP instruction which can also be used to read the processor ID, user-mode RDPID is not disabled by CR4.TSD=1.
34. For MOVDIR64, the destination address given by ES:reg must be 64-byte aligned.
    The operand size for the register argument is given by the address size, which may be overridden by the 67h prefix.
    The 64-byte memory source argument does not need to be 64-byte aligned, and is not guaranteed to be read atomically.
35. The WBNOINVD instruction will execute as WBINVD if run on a system that doesn't support the WBNOINVD extension.
    WBINVD differs from WBNOINVD in that WBINVD will invalidate all cache lines after writeback.
36. ^ In initial implementations, the PREFETCHIT0 and PREFETCHIT1 instructions will perform code prefetch only when using the RIP-relative addressing mode and act as NOPs otherwise.
    The PREFETCHI instructions are hint instructions only - if an attempt is made to prefetch an invalid address, the instructions will act as NOPs with no exceptions generated. On processors that support Long-NOP but do not support the PREFETCHI instructions, these instructions will always act as NOPs.

Added with other Intel-specific extensions

temp1 := 
EFLAGS := CMP temp1, reg1 // sets EFLAGS like regular compare
reg1 := temp1
if( condition )
     := temp1 + reg2

1. ^ The branch hint mnemonics HWNT and HST are listed in early Willamette documentation only - later Intel documentation lists the branch hint prefixes without assigning them a mnemonic.

   Intel XED uses the mnemonics hint-taken and hint-not-taken for these branch hints.

2. ^ The 2E and 3E prefixes are interpreted as branch hints only when used with the Jcc conditional branch instructions (opcodes 70..7F and 0F 80..8F) - when used with other opcodes, they may take other meanings (e.g. for instructions with memory operands outside 64-bit mode, they will work as segment-override prefixes CS: and DS:, respectively). On processors that don't support branch hints, these prefixes are accepted but ignored when used with Jcc.
3. Branch hints are supported on all NetBurst (Pentium 4 family) processors - but not supported on any other known processor prior to their re-introduction in "Redwood Cove" CPUs, starting with "Meteor Lake" in 2023.
4. The leaf functions defined for ENCLS (selected by EAX) are:

   EAX	Function
   0 (ECREATE)	Create an enclave
   1 (EADD)	Add a page
   2 (EINIT)	Initialize an enclave
   3 (EREMOVE)	Remove a page from EPC (Enclave Page Cache)
   4 (EDBGRD)	Read data by debugger
   5 (EDBGWR)	Write data by debugger
   6 (EEXTEND)	Extend EPC page measurement
   7 (ELDB)	Load an EPC page as blocked
   8 (ELDU)	Load an EPC page as unblocked
   9 (EBLOCK)	Block an EPC page
   A (EPA)	Add version array
   B (EWB)	Writeback/invalidate EPC page
   C (ETRACK)	Activate EBLOCK checks
   Added with SGX2
   D (EAUG)	Add page to initialized enclave
   E (EMODPTR)	Restrict permissions of EPC page
   F (EMODT)	Change type of EPC page
   Added with OVERSUB
   10 (ERDINFO)	Read EPC page type/status info
   11 (ETRACKC)	Activate EBLOCK checks
   12 (ELDBC)	Load EPC page as blocked with enhanced error reporting
   13 (ELDUC)	Load EPC page as unblocked with enhanced error reporting
   Other
   18 (EUPDATESVN)	Update SVN (Security Version Number) after live microcode update

   Any unsupported value in EAX causes a #GP exception.

5. SGX is deprecated on desktop/laptop processors from 11th generation (Rocket Lake, Tiger Lake) onwards, but continues to be available on Xeon-branded server parts.
6. The leaf functions defined for ENCLU (selected by EAX) are:

   EAX	Function
   0 (EREPORT)	Create a cryptographic report
   1 (EGETKEY)	Create a cryptographic key
   2 (EENTER)	Enter an Enclave
   3 (ERESUME)	Re-enter an Enclave
   4 (EEXIT)	Exit an Enclave
   Added with SGX2
   5 (EACCEPT)	Accept changes to EPC page
   6 (EMODPE)	Extend EPC page permissions
   7 (EACCEPTCOPY)	Initialize pending page
   Added with TDX
   8 (EVERIFYREPORT2)	Verify a cryptographic report of a trust domain
   Added with AEX-Notify
   9 (EDECCSSA)	Decrement TCS.CSSA

   Any unsupported value in EAX causes a #GP exception.
   The EENTER and ERESUME functions cannot be executed inside an SGX enclave – the other functions can only be executed inside an enclave.

7. ENCLU can only be executed in ring 3, not rings 0/1/2.
8. The leaf functions defined for ENCLV (selected by EAX) are:

   EAX	Function
   Added with OVERSUB
   0 (EDECVIRTCHILD)	Decrement VIRTCHILDCNT in SECS
   1 (EINCVIRTCHILD)	Increment VIRTCHILDCNT in SECS
   2 (ESETCONTEXT)	Set ENCLAVECONTEXT field in SECS

   Any unsupported value in EAX causes a #GP exception.
   The ENCLV instruction is only present on systems that support the EPC Oversubscription Extensions to SGX ("OVERSUB").

9. ENCLV is only available if Intel VMX operation is enabled with VMXON, and will produce #UD otherwise.
10. For PTWRITE, the write to the Processor Trace Packet will only happen if a set of enable-bits (the "TriggerEn", "ContextEn", "FilterEn" bits of the RTIT_STATUS MSR and the "PTWEn" bit of the RTIT_CTL MSR) are all set to 1.
    The PTWRITE instruction is indicated in the SDM to cause an #UD exception if the 66h instruction prefix is used, regardless of other prefixes.
11. The leaf functions defined for PCONFIG (selected by EAX) are:

    EAX	Function
    0	MKTME_KEY_PROGRAM: Program key and encryption mode to use with an TME-MK Key ID.
    Added with TSE
    1	TSE_KEY_PROGRAM: Direct key programming for TSE.
    2	TSE_KEY_PROGRAM_WRAPPED: Wrapped key programming for TSE.

    Any unsupported value in EAX causes a #GP(0) exception.

12. For CLDEMOTE, the cache level that it will demote a cache line to is implementation-dependent.
    Since the instruction is considered a hint, it will execute as a NOP without any exceptions if the provided memory address is invalid or not in the L1 cache. It may also execute as a NOP under other implementation-dependent circumstances as well.
    On systems that do not support the CLDEMOTE extension, it executes as a NOP.
13. Intel documentation lists Tremont and Alder Lake as the processors in which CLDEMOTE was introduced. However, as of May 2022, no Tremont or Alder Lake models have been observed to have the CPUID feature bit for CLDEMOTE set, while several of them have the CPUID bit cleared.
    As of April 2023, the CPUID feature bit for CLDEMOTE has been observed to be set for Sapphire Rapids.
14. For UMONITOR, the operand size of the address argument is given by the address size, which may be overridden by the 67h prefix. The default segment used is DS:, which can be overridden with a segment prefix.
15. ^ For the UMWAIT and TPAUSE instructions, the operating system can use the IA32_UMWAIT_CONTROL MSR to limit the maximum amount of time that a single UMWAIT/TPAUSE invocation is permitted to wait. The UMWAIT and TPAUSE instructions will set RFLAGS.CF to 1 if they reached the IA32_UMWAIT_CONTROL-defined time limit and 0 otherwise.
16. TPAUSE and UMWAIT can be run outside Ring 0 only if CR4.TSD=0.
17. For the register argument to the UMWAIT and TPAUSE instructions, the following flag bits are supported:

    Bits	Usage
    0	Preferred optimization state. 0 = C0.2 (slower wakeup, improves performance of other SMT threads on same core) 1 = C0.1 (faster wakeup)
    31:1	(Reserved)

18. While serialization can be performed with older instructions such as e.g. CPUID and IRET, these instructions perform additional functions, causing side-effects and reduced performance when stand-alone instruction serialization is needed. (CPUID additionally has the issue that it causes a mandatory #VMEXIT when executed under virtualization, which causes a very large overhead.) The SERIALIZE instruction performs serialization only, avoiding these added costs.
19. A bitmap of CPU history components that can be reset through HRESET is provided by CPUID.(EAX=20h,ECX=0):EBX.
    As of July 2023, the following bits are defined:

    Bit	Usage
    0	Intel Thread Director history
    31:1	(Reserved)

20. The register argument to SENDUIPI is an index to pick an entry from the UITT (User-Interrupt Target Table, a table specified by the new UINTR_TT and UINT_MISC MSRs.)
21. On Sapphire Rapids processors, the UIRET instruction always sets UIF (User Interrupt Flag) to 1. On Sierra Forest and later processors, UIRET will set UIF to the value of bit 1 of the value popped off the stack for RFLAGS - this functionality is indicated by CPUID.(EAX=7,ECX=1):EDX.
22. For ENQCMD and EMQCMDS, the operand-size of the register argument is given by the current address-size, which can be overridden with the 67h prefix.
23. ^ For the RDMSRLIST and WRMSRLIST instructions, the addresses specified in the RSI and RDI registers must be 8-byte aligned.
24. The condition codes supported for the CMPccXADD instructions (opcode VEX.128.66.0F38 Ex /r with the x nibble specifying the condition) are:

    x	cc	Condition (EFLAGS)
    0	O	OF=1: "Overflow"
    1	NO	OF=0: "Not Overflow"
    2	B	CF=1: "Below"
    3	NB	CF=0: "Not Below"
    4	Z	ZF=1: "Zero"
    5	NZ	ZF=0: "Not Zero"
    6	BE	(CF=1 or ZF=1): "Below or Equal"
    7	NBE	(CF=0 and ZF=0): "Not Below or Equal"
    8	S	SF=1: "Sign"
    9	NS	SF=0: "Not Sign"
    A	P	PF=1: "Parity"
    B	NP	PF=0: "Not Parity"
    C	L	SF≠OF: "Less"
    D	NL	SF=OF: "Not Less"
    E	LE	(ZF=1 or SF≠OF): "Less or Equal"
    F	NLE	(ZF=0 and SF=OF): "Not Less or Equal"

25. Even though the CMPccXADD instructions perform a locked memory operation, they do not require or accept the LOCK (F0h) prefix - attempting to use this prefix results in #UD.

Added with other AMD-specific extensions

1. The standard way to access the CR8 register is to use an encoding that makes use of the REX.R prefix, e.g. 44 0F 20 07 (MOV RDI,CR8). However, the REX.R prefix is only available in 64-bit mode.
   The AltMovCr8 extension adds an additional method to access CR8, using the F0 (LOCK) prefix instead of REX.R – this provides access to CR8 outside 64-bit mode.
2. ^ Like other variants of MOV to/from the CRx registers, the AltMovCr8 encodings ignore the top 2 bits of the instruction's ModR/M byte, and always execute as if these two bits are set to 11b.
   The AltMovCr8 encodings are available in 64-bit mode. However, combining the LOCK prefix with the REX.R prefix is not permitted and will cause an #UD exception.
3. Support for AltMovCR8 was added in stepping F of the AMD K8, and is not available on earlier steppings.
4. For CLZERO, the address size and 67h prefix control whether to use AX, EAX or RAX as address. The default segment DS: can be overridden by a segment-override prefix. The provided address does not need to be aligned – hardware will align it as necessary.
   The CLZERO instruction is intended for recovery from otherwise-fatal Machine Check errors. It is non-cacheable, cannot be used to allocate a cache line without a memory access, and should not be used for fast memory clears.
5. The register numbering used by RDPRU does not necessarily match that of RDMSR/WRMSR.
   The registers supported by RDPRU as of December 2022 are:

   ECX	Register
   0	MPERF (MSR 0E7h: Maximum Performance Frequency Clock Count)
   1	APERF (MSR 0E8h: Actual Performance Frequency Clock Count)

   Unsupported values in ECX return 0.

6. If CR4.TSD=1, then the RDPRU instruction can only run in ring 0.

x87 floating-point instructions

The x87 coprocessor, if present, provides support for floating-point arithmetic. The coprocessor provides eight data registers, each holding one 80-bit floating-point value (1 sign bit, 15 exponent bits, 64 mantissa bits) – these registers are organized as a stack, with the top-of-stack register referred to as "st" or "st(0)", and the other registers referred to as st(1),st(2),...st(7). It additionally provides a number of control and status registers, including "PC" (precision control, to control whether floating-point operations should be rounded to 24, 53 or 64 mantissa bits) and "RC" (rounding control, to pick rounding-mode: round-to-zero, round-to-positive-infinity, round-to-negative-infinity, round-to-nearest-even) and a 4-bit condition code register "CC", whose four bits are individually referred to as C0,C1,C2 and C3). Not all of the arithmetic instructions provided by x87 obey PC and RC.

Original 8087 instructions

Instruction description	Mnemonic	Opcode	Additional items
x87 Non-Waiting FPU Control Instructions			Waiting mnemonic
Initialize x87 FPU	FNINIT	DB E3	FINIT
Load x87 Control Word	FLDCW m16	D9 /5	(none)
Store x87 Control Word	FNSTCW m16	D9 /7	FSTCW
Store x87 Status Word	FNSTSW m16	DD /7	FSTSW
Clear x87 Exception Flags	FNCLEX	DB E2	FCLEX
Load x87 FPU Environment	FLDENV m112/m224	D9 /4	(none)
Store x87 FPU Environment	FNSTENV m112/m224	D9 /6	FSTENV
Save x87 FPU State, then initialize x87 FPU	FNSAVE m752/m864	DD /6	FSAVE
Restore x87 FPU State	FRSTOR m752/m864	DD /4	(none)
Enable Interrupts (8087 only)	FNENI	DB E0	FENI
Disable Interrupts (8087 only)	FNDISI	DB E1	FDISI
x87 Floating-point Load/Store/Move Instructions			precision control	rounding control
Load floating-point value onto stack	FLD m32	D9 /0	No	—
	FLD m64	DD /0
	FLD m80	DB /5
	FLD st(i)	D9 C0+i
Store top-of-stack floating-point value to memory or stack register	FST m32	D9 /2	No	Yes
	FST m64	DD /2
	FST st(i)	DD D0+i	No	—
Store top-of-stack floating-point value to memory or stack register, then pop	FSTP m32	D9 /3	No	Yes
	FSTP m64	DD /3
	FSTP m80	DB /7	No	—
	FSTP st(i)	DD D8+i
		DF D0+i
		DF D8+i
Push +0.0 onto stack	FLDZ	D9 EE	No	—
Push +1.0 onto stack	FLD1	D9 E8
Push π (approximately 3.14159) onto stack	FLDPI	D9 EB	No	387
Push ${\displaystyle \log _{2}\left(10\right)}$ (approximately 3.32193) onto stack	FLDL2T	D9 E9
Push ${\displaystyle \log _{2}\left(e\right)}$ (approximately 1.44269) onto stack	FLDL2E	D9 EA
Push ${\displaystyle \log _{10}\left(2\right)}$ (approximately 0.30103) onto stack	FLDLG2	D9 EC
Push ${\displaystyle \ln \left(2\right)}$ (approximately 0.69315) onto stack	FLDLN2	D9 ED
Exchange top-of-stack register with other stack register	FXCH st(i)	D9 C8+i	No	—
		DD C8+i
		DF C8+i
x87 Integer Load/Store Instructions			precision control	rounding control
Load signed integer value onto stack from memory, with conversion to floating-point	FILD m16	DF /0	No	—
	FILD m32	DB /0
	FILD m64	DF /5
Store top-of-stack value to memory, with conversion to signed integer	FIST m16	DF /2	No	Yes
	FIST m32	DB /2
Store top-of-stack value to memory, with conversion to signed integer, then pop stack	FISTP m16	DF /3	No	Yes
	FISTP m32	DB /3
	FISTP m64	DF /7
Load 18-digit Binary-Coded-Decimal integer value onto stack from memory, with conversion to floating-point	FBLD m80	DF /4	No	—
Store top-of-stack value to memory, with conversion to 18-digit Binary-Coded-Decimal integer, then pop stack	FBSTP m80	DF /6	No	387
x87 Basic Arithmetic Instructions			precision control	rounding control
Floating-point add dst <- dst + src	FADD m32	D8 /0	Yes	Yes
	FADD m64	DC /0
	FADD st,st(i)	D8 C0+i
	FADD st(i),st	DC C0+i
Floating-point multiply dst <- dst * src	FMUL m32	D8 /1	Yes	Yes
	FMUL m64	DC /1
	FMUL st,st(i)	D8 C8+i
	FMUL st(i),st	DC C8+i
Floating-point subtract dst <- dst – src	FSUB m32	D8 /4	Yes	Yes
	FSUB m64	DC /4
	FSUB st,st(i)	D8 E0+i
	FSUB st(i),st	DC E8+i
Floating-point reverse subtract dst <- src – dst	FSUBR m32	D8 /5	Yes	Yes
	FSUBR m64	DC /5
	FSUBR st,st(i)	D8 E8+i
	FSUBR st(i),st	DC E0+i
Floating-point divide dst <- dst / src	FDIV m32	D8 /6	Yes	Yes
	FDIV m64	DC /6
	FDIV st,st(i)	D8 F0+i
	FDIV st(i),st	DC F8+i
Floating-point reverse divide dst <- src / dst	FDIVR m32	D8 /7	Yes	Yes
	FDIVR m64	DC /7
	FDIVR st,st(i)	D8 F8+i
	FDIVR st(i),st	DC F0+i
Floating-point compare CC <- result_of( st(0) – src ) Same operation as subtract, except that it updates the x87 CC status register instead of any of the FPU stack registers	FCOM m32	D8 /2	No	—
	FCOM m64	DC /2
	FCOM st(i)	D8 D0+i
		DC D0+i
x87 Basic Arithmetic Instructions with Stack Pop			precision control	rounding control
Floating-point add and pop	FADDP st(i),st	DE C0+i	Yes	Yes
Floating-point multiply and pop	FMULP st(i),st	DE C8+i	Yes	Yes
Floating-point subtract and pop	FSUBP st(i),st	DE E8+i	Yes	Yes
Floating-point reverse-subtract and pop	FSUBRP st(i),st	DE E0+i	Yes	Yes
Floating-point divide and pop	FDIVP st(i),st	DE F8+i	Yes	Yes
Floating-point reverse-divide and pop	FDIVRP st(i),st	DE F0+i	Yes	Yes
Floating-point compare and pop	FCOMP m32	D8 /3	No	—
	FCOMP m64	DC /3
	FCOMP st(i)	D8 D8+i
		DC D8+i
		DE D0+i
Floating-point compare to st(1), then pop twice	FCOMPP	DE D9	No	—
x87 Basic Arithmetic Instructions with Integer Source Argument			precision control	rounding control
Floating-point add by integer	FIADD m16	DA /0	Yes	Yes
	FIADD m32	DE /0
Floating-point multiply by integer	FIMUL m16	DA /1	Yes	Yes
	FIMUL m32	DE /1
Floating-point subtract by integer	FISUB m16	DA /4	Yes	Yes
	FISUB m32	DE /4
Floating-point reverse-subtract by integer	FISUBR m16	DA /5	Yes	Yes
	FISUBR m32	DE /5
Floating-point divide by integer	FIDIV m16	DA /6	Yes	Yes
	FIDIV m32	DE /6
Floating-point reverse-divide by integer	FIDIVR m16	DA /7	Yes	Yes
	FIDIVR m32	DE /7
Floating-point compare to integer	FICOM m16	DA /2	No	—
	FICOM m32	DE /2
Floating-point compare to integer, and stack pop	FICOMP m16	DA /3	No	—
	FICOMP m32	DE /3
x87 Additional Arithmetic Instructions			precision control	rounding control
Floating-point change sign	FCHS	D9 E0	No	—
Floating-point absolute value	FABS	D9 E1	No	—
Floating-point compare top-of-stack value to 0	FTST	D9 E4	No	—
Classify top-of-stack st(0) register value. The classification result is stored in the x87 CC register.	FXAM	D9 E5	No	—
Split the st(0) value into two values E and M representing the exponent and mantissa of st(0). The split is done such that ${\displaystyle M*2^{E}=st(0)}$, where E is an integer and M is a number whose absolute value is within the range ${\displaystyle 1\leq \left|M\right|<2}$.   st(0) is then replaced with E, after which M is pushed onto the stack.	FXTRACT	D9 F4	No	—
Floating-point partial remainder (not IEEE 754 compliant):$${\displaystyle Q\leftarrow {\mathtt {IntegerRoundToZero}}\left({\frac {st(0)}{st(1)}}\right)}$$$${\displaystyle st(0)\leftarrow st(0)-st(1)*Q}$$	FPREM	D9 F8	No	—
Floating-point square root	FSQRT	D9 FA	Yes	Yes
Floating-point round to integer	FRNDINT	D9 FC	No	Yes
Floating-point power-of-2 scaling. Rounds the value of st(1) to integer with round-to-zero, then uses it as a scale factor for st(0):$${\displaystyle st(0)\leftarrow st(0)*2^{{\mathtt {IntegerRoundToZero}}\left(st(1)\right)}}$$	FSCALE	D9 FD	No	Yes
x87 Transcendental Instructions			Source operand range restriction
Base-2 exponential minus 1, with extra precision for st(0) close to 0:$${\displaystyle st(0)\leftarrow 2^{st(0)}-1}$$	F2XM1	D9 F0	8087: ${\displaystyle 0\leq st(0)\leq {\frac {1}{2}}}$ 80387: ${\displaystyle -1\leq st(0)\leq 1}$
Base-2 Logarithm:$${\displaystyle st(1)\leftarrow st(1)*\log _{2}\left(st(0)\right)}$$followed by stack pop	FYL2X	D9 F1	no restrictions
Partial Tangent: Computes from st(0) a pair of values X and Y, such that$${\displaystyle \tan \left(st(0)\right)={\frac {Y}{X}}}$$The Y value replaces the top-of-stack value, and then X is pushed onto the stack. On 80387 and later x87, but not original 8087, X is always 1.0	FPTAN	D9 F2	8087: ${\displaystyle 0\leq \left|st(0)\right|\leq {\frac {\pi }{4}}}$ 80387: ${\displaystyle 0\leq \left|st(0)\right|<2^{63}}$
Two-argument arctangent with quadrant adjustment:$${\displaystyle st(1)\leftarrow \arctan \left({\frac {st(1)}{st(0)}}\right)}$$ followed by stack pop	FPATAN	D9 F3	8087: ${\displaystyle \left|st(1)\right|\leq \left|st(0)\right|<\infty }$ 80387: no restrictions
Base-2 Logarithm plus 1, with extra precision for st(0) close to 0:$${\displaystyle st(1)\leftarrow st(1)*\log _{2}\left(st(0)+1\right)}$$followed by stack pop	FYL2XP1	D9 F9	Intel: ${\displaystyle \left|st(0)\right|<\left(1-{\sqrt {\frac {1}{2}}}\right)}$ AMD: ${\displaystyle \left({\sqrt {\frac {1}{2}}}-1\right)<st(0)<\left({\sqrt {2}}-1\right)}$
Other x87 Instructions
No operation	FNOP	D9 D0
Decrement x87 FPU Register Stack Pointer	FDECSTP	D9 F6
Increment x87 FPU Register Stack Pointer	FINCSTP	D9 F7
Free x87 FPU Register	FFREE st(i)	DD C0+i
Check and handle pending unmasked x87 FPU exceptions	WAIT, FWAIT	9B
Floating-point store and pop, without stack underflow exception	FSTPNCE st(i)	D9 D8+i
Free x87 register, then stack pop	FFREEP st(i)	DF C0+i

1. x87 coprocessors (other than the 8087) handle exceptions in a fairly unusual way. When an x87 instruction generates an unmasked arithmetic exception, it will still complete without causing a CPU fault – instead of causing a fault, it will record within the coprocessor information needed to handle the exception (instruction pointer, opcode, data pointer if the instruction had a memory operand) and set FPU status-word flag to indicate that a pending exception is present. This pending exception will then cause a CPU fault when the next x87, MMX or WAIT instruction is executed.
   The exception to this is x87's "Non-Waiting" instructions, which will execute without causing such a fault even if a pending exception is present (with some caveats, see application note AP-578). These instructions are mostly control instructions that can inspect and/or modify the pending-exception state of the x87 FPU.
2. For each non-waiting x87 instruction whose mnemonic begins with FN, there exists a pseudo-instruction that has the same mnemonic except without the N. These pseudo-instructions consist of a WAIT instruction (opcode 9B) followed by the corresponding non-waiting x87 instruction. For example:
   • FNCLEX is an instruction with the opcode DB E2. The corresponding pseudo-instruction FCLEX is then encoded as 9B DB E2.
   • FNSAVE ES: is an instruction with the opcode 26 DD 77 06. The corresponding pseudo-instruction FSAVE ES: is then encoded as 9B 26 DD 77 06
   These pseudo-instructions are commonly recognized by x86 assemblers and disassemblers and treated as single instructions, even though all x86 CPUs with x87 coprocessors execute them as a sequence of two instructions.
3. ^ On 80387 and later x87 FPUs, FLDENV, F(N)STENV, FRSTOR and F(N)SAVE exist in 16-bit and 32-bit variants. The 16-bit variants will load/store a 14-byte floating-point environment data structure to/from memory – the 32-bit variants will load/store a 28-byte data structure instead. (F(N)SAVE/FRSTOR will additionally load/store an additional 80 bytes of FPU data register content after the FPU environment, for a total of 94 or 108 bytes). The choice between the 16-bit and 32-bit variants is based on the CS.D bit and the presence of the 66h instruction prefix. On 8087 and 80287, only the 16-bit variants are available.
   64-bit variants of these instructions do not exist – using REX.W under x86-64 will cause the 32-bit variants to be used. Since these can only load/store the bottom 32 bits of FIP and FDP, it is recommended to use FXSAVE64/FXRSTOR64 instead if 64-bit operation is desired.
4. ^ In the case of an x87 instruction producing an unmasked FPU exception, the 8087 FPU will signal an IRQ some indeterminate time after the instruction was issued. This may not always be possible to handle, and so the FPU offers the F(N)DISI and F(N)ENI instructions to set/clear the Interrupt Mask bit (bit 7) of the x87 Control Word, to control the interrupt.
   Later x87 FPUs, from 80287 onwards, changed the FPU exception mechanism to instead produce a CPU exception on the next x87 instruction. This made the Interrupt Mask bit unnecessary, so it was removed. In later Intel x87 FPUs, the F(N)ENI and F(N)DISI instructions were kept for backwards compatibility, executing as NOPs that do not modify any x87 state.
5. ^ FST/FSTP with an 80-bit destination (m80 or st(i)) and an sNaN source value will produce exceptions on AMD but not Intel FPUs.
6. FSTP ST(0) is a commonly used idiom for popping a single register off the x87 register stack.
7. ^ Intel x87 alias opcode. Use of this opcode is not recommended.
   On the Intel 8087 coprocessor, several reserved opcodes would perform operations behaving similarly to existing defined x87 instructions. These opcodes were documented for the 8087 and 80287, but then omitted from later manuals until the October 2017 update of the Intel SDM.
   They are present on all known Intel x87 FPUs but unavailable on some older non-Intel FPUs, such as AMD Geode GX/LX, DM&P Vortex86 and NexGen 586PF.
8. ^ On the 8087 and 80287, FBSTP and the load-constant instructions always use the round-to-nearest rounding mode. On the 80387 and later x87 FPUs, these instructions will use the rounding mode specified in the x87 RC register.
9. ^ For the FADDP, FSUBP, FSUBRP, FMULP, FDIVP, FDIVRP, FCOM, FCOMP and FXCH instructions, x86 assemblers/disassemblers may recognize variants of the instructions with no arguments. Such variants are equivalent to variants using st(1) as their first argument.
10. On Intel Pentium and later processors, FXCH is implemented as a register renaming rather than a true data move. This has no semantic effect, but enables zero-cycle-latency operation. It also allows the instruction to break data dependencies for the x87 top-of-stack value, improving attainable performance for code optimized for these processors.
11. The result of executing the FBLD instruction on non-BCD data is undefined.
12. On early Intel Pentium processors, floating-point divide was subject to the Pentium FDIV bug. This also affected instructions that perform divide as part of their operations, such as FPREM and FPATAN.
13. The FXAM instruction will set C0, C2 and C3 based on value type in st(0) as follows:

    C3	C2	C0	Classification
    0	0	0	Unsupported (unnormal or pseudo-NaN)
    0	0	1	NaN
    0	1	0	Normal finite number
    0	1	1	Infinity
    1	0	0	Zero
    1	0	1	Empty
    1	1	0	Denormal number
    1	1	1	Empty (may occur on 8087/80287 only)

    C1 is set to the sign-bit of st(0), regardless of whether st(0) is Empty or not.

14. For FXTRACT, if st(0) is zero or ±∞, then M is set equal to st(0). If st(0) is zero, E is set to 0 on 8087/80287 but -∞ on 80387 and later. If st(0) is ±∞, then E is set to +∞.
15. For FPREM, if the quotient Q is larger than ${\displaystyle 2^{63}}$, then the remainder calculation may have been done only partially – in this case, the FPREM instruction will need to be run again in order to complete the remainder calculation. This is indicated by the instruction setting C2 to 1.
    If the instruction did complete the remainder calculation, it will set C2 to 0 and set the three bits {C0,C3,C1} to the bottom three bits of the quotient Q.
    On 80387 and later, if the instruction didn't complete the remainder calculation, then the computed remainder Q used for argument reduction will have been rounded to a multiple of 8 (or larger power-of-2), so that the bottom 3 bits of the quotient can still be correctly retrieved in a later pass that does complete the remainder calculation.
16. The remainder computation done by the FPREM instruction is always exact with no roundoff errors.
17. For the FSCALE instruction on 8087 and 80287, st(1) is required to be in the range ${\displaystyle -2^{15}\leq st(1)<2^{15}}$. Also, its absolute value must be either 0 or at least 1. If these requirements are not satisfied, the result is undefined.
    These restrictions were removed in the 80387.
18. For FSCALE, rounding is only applied in the case of overflow, underflow or subnormal result.
19. The x87 transcendental instructions do not obey PC or RC, but instead compute full 80-bit results. These results are not necessarily correctly rounded (see Table-maker's dilemma) – they may have an error of up to ±1 ulp on Pentium or later, or up to ±1.5 ulps on earlier x87 coprocessors.
20. ^ For the FYL2X and FYL2XP1 instructions, the maximum error bound of ±1 ulp only holds for st(1)=1.0 – for other values of st(1), the error bound is increased to ±1.35 ulps.
21. For FPATAN, the following adjustments are done as compared to just computing a one-argument arctangent of the ratio ${\displaystyle {\frac {st(1)}{st(0)}}}$:
    • If both st(0) and st(1) are ±∞, then the arctangent is computed as if each of st(0) and st(1) had been replaced with ±1 of the same sign. This produces a result that is an odd multiple of ${\displaystyle {\frac {\pi }{4}}}$.
    • If both st(0) and st(1) are ±0, then the arctangent is computed as if st(0) but not st(1) had been replaced with ±1 of the same sign, producing a result of ±0 or ${\displaystyle \pm \pi }$.
    • If st(0) is negative (has sign bit set), then an addend of ${\displaystyle \pm \pi }$ with the same sign as st(1) is added to the result.
22. While FNOP is a no-op in the sense that will leave the x87 FPU register stack unmodified, it may still modify FIP and CC, and it may fault if a pending x87 FPU exception is present.

x87 instructions added in later processors

Instruction description	Mnemonic	Opcode	Additional items
x87 Non-Waiting Control Instructions added in 80287			Waiting mnemonic
Notify FPU of entry into Protected Mode	FNSETPM	DB E4	FSETPM
Store x87 Status Word to AX	FNSTSW AX	DF E0	FSTSW AX
x87 Instructions added in 80387			Source operand range restriction
Floating-point unordered compare. Similar to the regular floating-point compare instruction FCOM, except will not produce an exception in response to any qNaN operands.	FUCOM st(i)	DD E0+i	no restrictions
Floating-point unordered compare and pop	FUCOMP st(i)	DD E8+i
Floating-point unordered compare to st(1), then pop twice	FUCOMPP	DA E9
IEEE 754 compliant floating-point partial remainder.	FPREM1	D9 F5
Floating-point sine and cosine. Computes two values ${\displaystyle S=\sin \left(k*st(0)\right)}$ and ${\displaystyle C=\cos \left(k*st(0)\right)}$  Top-of-stack st(0) is replaced with S, after which C is pushed onto the stack.	FSINCOS	D9 FB	${\displaystyle \left|st(0)\right|<2^{63}}$
Floating-point sine.$${\displaystyle st(0)\leftarrow \sin \left(k*st(0)\right)}$$	FSIN	D9 FE
Floating-point cosine.$${\displaystyle st(0)\leftarrow \cos \left(k*st(0)\right)}$$	FCOS	D9 FF
x87 Instructions added in Pentium Pro			Condition for conditional moves
Floating-point conditional move to st(0) based on EFLAGS	FCMOVB st(0),st(i)	DA C0+i	below (CF=1)
	FCMOVE st(0),st(i)	DA C8+i	equal (ZF=1)
	FCMOVBE st(0),st(i)	DA D0+i	below or equal (CF=1 or ZF=1)
	FCMOVU st(0),st(i)	DA D8+i	unordered (PF=1)
	FCMOVNB st(0),st(i)	DB C0+i	not below (CF=0)
	FCMOVNE st(0),st(i)	DB C8+i	not equal (ZF=0)
	FCMOVNBE st(0),st(i)	DB D0+i	not below or equal (CF=0 and ZF=0)
	FCMOVNU st(0),st(i)	DB D8+i	not unordered (PF=0)
Floating-point compare and set EFLAGS. Differs from the older FCOM floating-point compare instruction in that it puts its result in the integer EFLAGS register rather than the x87 CC register.	FCOMI st(0),st(i)	DB F0+i
Floating-point compare and set EFLAGS, then pop	FCOMIP st(0),st(i)	DF F0+i
Floating-point unordered compare and set EFLAGS	FUCOMI st(0),st(i)	DB E8+i
Floating-point unordered compare and set EFLAGS, then pop	FUCOMIP st(0),st(i)	DF E8+i
x87 Non-Waiting Instructions added in Pentium II, AMD K7 and SSE			64-bit mnemonic (REX.W prefix)
Save x87, MMX and SSE state to 512-byte data structure	FXSAVE m512byte	NP 0F AE /0	FXSAVE64 m512byte
Restore x87, MMX and SSE state from 512-byte data structure	FXRSTOR m512byte	NP 0F AE /1	FXRSTOR64 m512byte
x87 Instructions added as part of SSE3
Floating-point store integer and pop, with round-to-zero	FISTTP m16	DF /1
	FISTTP m32	DB /1
	FISTTP m64	DD /1

1. The x87 FPU needs to know whether it is operating in Real Mode or Protected Mode because the floating-point environment accessed by the F(N)SAVE, FRSTOR, FLDENV and F(N)STENV instructions has different formats in Real Mode and Protected Mode. On 80287, the F(N)SETPM instruction is required to communicate the real-to-protected mode transition to the FPU. On 80387 and later x87 FPUs, real↔protected mode transitions are communicated automatically to the FPU without the need for any dedicated instructions – therefore, on these FPUs, FNSETPM executes as a NOP that does not modify any FPU state.
2. Not including discontinued instructions specific to particular 80387-compatible FPU models.
3. ^ For the FUCOM and FUCOMP instructions, x86 assemblers/disassemblers may recognize variants of the instructions with no arguments. Such variants are equivalent to variants using st(1) as their first argument.
4. The 80387 FPREM1 instruction differs from the older FPREM (D9 F8) instruction in that the quotient Q is rounded to integer with round-to-nearest-even rounding rather than the round-to-zero rounding used by FPREM. Like FPREM, FPREM1 always computes an exact result with no roundoff errors. Like FPREM, it may also perform a partial computation if the quotient is too large, in which case it must be run again.
5. ^ Due to the x87 FPU performing argument reduction for sin/cos with only about 68 bits of precision, the value of k used in the calculation of FSIN, FCOS and FSINCOS is not precisely 1.0, but instead given by$${\displaystyle k{=}{\frac {2^{66}*\pi }{\lfloor 2^{66}*\pi \rfloor }}\approx 1.0000000000000000000012874}$$This argument reduction inaccuracy also affects the FPTAN instruction.
6. The FCOMI, FCOMIP, FUCOMI and FUCOMIP instructions write their results to the ZF, CF and PF bits of the EFLAGS register. On Intel but not AMD processors, the SF, AF and OF bits of EFLAGS are also zeroed out by these instructions.
7. The FXSAVE and FXRSTOR instructions were added in the "Deschutes" revision of Pentium II, and are not present in earlier "Klamath" revision.
   They are also present in AMD K7.
   They are also considered an integral part of SSE and are therefore present in all processors with SSE.
8. ^ The FXSAVE and FXRSTOR instructions will save/restore SSE state only on processors that support SSE. Otherwise, they will only save/restore x87 and MMX state.
   The x87 section of the state saved/restored by FXSAVE/FXRSTOR has a completely different layout than the data structure of the older F(N)SAVE/FRSTOR instructions, enabling faster save/restore by avoiding misaligned loads and stores.
9. ^ When floating-point emulation is enabled with CR0.EM=1, FXSAVE(64) and FXRSTOR(64) are considered to be x87 instructions and will accordingly produce an #NM (device-not-available) exception. Other than WAIT, these are the only opcodes outside the D8..DF ESC opcode space that exhibit this behavior. (All opcodes in D8..DF will produce #NM if CR0.EM=1, even for undefined opcodes that would produce #UD otherwise.)
10. Unlike the older F(N)SAVE instruction, FXSAVE will not initialize the FPU after saving its state to memory, but instead leave the x87 coprocessor state unmodified.

SIMD instructions

Cryptographic instructions

Virtualization instructions

Other instructions

x86 also includes discontinued instruction sets which are no longer supported by Intel and AMD, and undocumented instructions which execute but are not officially documented.

Undocumented x86 instructions

The x86 CPUs contain undocumented instructions which are implemented on the chips but not listed in some official documents. They can be found in various sources across the Internet, such as Ralf Brown's Interrupt List and at sandpile.org

Some of these instructions are widely available across many/most x86 CPUs, while others are specific to a narrow range of CPUs.

Undocumented instructions that are widely available across many x86 CPUs include

Undocumented instructions that appear only in a limited subset of x86 CPUs include