Extensions
Forms
1 (1 EVEX)
Data
Intel XED v2026.08.23

POP2P is POP2 with the push-pop acceleration hint: it loads two 64-bit registers from the stack and says the values were written by a matching PUSH2P. EVEX.W set to 1 is the only difference in the encoding, and the hint affects speed alone. POP2’s rules hold: RSP must be 16-byte aligned before it runs or it raises #GP, neither register may be RSP, and the two must differ or it raises #UD. It changes no flag.

The first register named takes the lower address, so restoring push2p r15, r14 takes pop2p r14, r15. A PUSH2P should meet a POP2P rather than two POPP, and a hint that breaks that rule loses the speed-up without changing the result.

Our GCC 14 and Clang 23 builds at -O2 with -mapxf pair them in the epilogue, as the PUSH2P page shows.

Forms

Every encoding of POP2P that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
POP2P r64, r64 POP2P_GPR64u64_GPR64u64_APX_N3EVEX.LLZ.NP.MAP4.W1 8F /0 ND=1APX_F + APX_NCI_NDD_NF

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

n1 = dest1.number
n2 = dest2.number
if n1 == 4 or n2 == 4 or n1 == n2:
    fault(UD)
if rsp % 16 != 0:
    fault(GP, 0)
v1 = load(rsp, 64)               # POP2 with the hint that a PUSH2P pushed
v2 = load(rsp + 8, 64)           # what it pops
rsp = rsp + 16
dest1.write(v1)
dest2.write(v2)

Not run on a processor: none of these processors has APX.

Operands

What each form reads and writes, as Intel XED records it: the operands of its syntax, in order, and the implicit ones that the syntax does not name. How to read.
OperandKindAction
POP2P r64, r64
r64explicitwrite
r64explicitwrite
stackimplicitread
rSPimplicitread, write

Flags

None: XED records no flag that the forms test or change.

Exceptions

The exception class is XED's name for the set of exception conditions that a form follows. How to read.

All forms
APX-EVEX-PP2

CPUID and processors

Each form belongs to an XED ISA set. A form can be used when the processor reports every CPUID bit of one of its ISA set's alternatives.

CPUID requirements and processors of the XED ISA sets above. Alternatives are separated by “or”; processors follow XED’s chip model, whose AMD processors end with Zen 2, and the CPU data of this site for Zen 3 to Zen 6.
ISA setCPUIDProcessors
APX_F_N3

APX_F + APX_NCI_NDD_NF
CPUID.(EAX=07H,ECX=1):EDX[21] APX_F
CPUID.(EAX=29H,ECX=0):EBX[0] APX_NCI_NDD_NF

Nova Lake, Diamond Rapids

More APX instructions

All 88 APX instructions

Sources

  1. Intel XED v2026.08.23 (commit 0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model.
  2. Intel Advanced Performance Extensions (Intel APX) Architecture Specification, revision 9.0 (355828-009, August 2026)

The tables are derived from Intel XED, Copyright Intel Corporation, licensed under the Apache License 2.0; x86-64.net converted and reformatted them. The text is our own.