Extensions
Forms
2 (2 Legacy)
Data
Intel XED v2026.08.23

AESDECLAST performs the final round of AES decryption on the 16-byte state in its first operand: InvShiftRows and InvSubBytes, then an XOR with the round key from the second operand. It is AESDEC without InvMixColumns, and every block decrypted with AESDEC ends with exactly one AESDECLAST. AESDEC’s page gives the whole sequence and the key schedule; AESENCLAST is the mirror image for encryption, and VAESDECLAST the VEX and EVEX forms.

The key it takes

Of the decryption keys, only the middle ones pass through AESIMC. The key of AESDECLAST is the first round key of the encryption schedule, k0, unchanged, and for AES-128 that is the cipher key itself. Passing AESIMC(k0) instead raises nothing; the plaintext simply comes out wrong.

A round that is only bytes

Without InvMixColumns, each byte of the result depends on one byte of the state: it goes through the inverse S-box, moves to where InvShiftRows puts it, and is XORed with a key byte. Zen 5’s recorded cases show the inverse S-box directly: a zero state and zero key gave 52H in every byte, the inverse S-box’s value for 0, and a state and key of all ones gave 82H, its value for FFH (7DH) XORed with FFH. With zero keys, AESDECLAST undoes AESENCLAST: the inverse S-box and InvShiftRows reverse SubBytes and ShiftRows.

Folding in the next XOR

The round key enters only through the final XOR, so it can absorb other data. CBC decryption XORs each decrypted block with the ciphertext before it, and AESDECLAST with k0 XORed with that ciphertext gives the plaintext in one step. The number of XORs stays the same, but the one with the key no longer waits for the rounds: it can run while the block is still being decrypted. Compilers do not make the change themselves: for _mm_xor_si128(_mm_aesdeclast_si128(s, k0), prev), GCC 14 and Clang 23 at -O2 (-maes) emit AESDECLAST followed by PXOR.

The legacy form keeps bits 128 and up of its register and needs a memory operand aligned to 16 bytes; the VEX form clears them and takes any address. AMD’s Zen 5 guide lists AESDECLAST like AESDEC: a latency of four cycles, two started per cycle.

In the optimization guide

What the optimization guide says about AESDECLAST, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Haswell and Broadwell

  • Integer execution and bypass: AESENC, AESENCLAST, AESDEC and AESDECLAST become one micro-op each, with a little less latency than before, which helps the modes that run several blocks at once, such as CBC decryption, and code that encrypts several buffers side by side.

Silvermont to Goldmont Plus

  • Vectors and cryptography: AES rounds and carry-less multiplication are slow on Silvermont and faster with each Goldmont. sources differ

Tremont

Forms

Every encoding of AESDECLAST that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
AESDECLAST xmm, xmm AESDECLAST_XMMdq_XMMdq66 0F 38 DF /rAES
AESDECLAST xmm, m128 AESDECLAST_XMMdq_MEMdq66 0F 38 DF /rAES

Data flow

Where the elements of the sources go, element 0 on the right; results that depend on a control value are drawn for an example. How to read.

Element-wise: each 128-bit block of the result comes from the 128-bit block in the same place in each source.
AESDECLAST: element by elementResult 128-bit block i comes from 128-bit block i of xmm1 and xmm2. Result 128-bit blocks: r0.0xmm1ar0xmm10xmm2or m128b

Result 128-bit block i comes from 128-bit block i of xmm1 and xmm2. Result 128-bit blocks: r0.

Operation

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

# the last round of the equivalent inverse
# cipher, which leaves out InvMixColumns
s = inv_sub_bytes(xmm1.read())   # xmm1: the state
s = inv_shift_rows(s)
xmm1.write(s ^ src2)             # the cipher's first round key
# bits 128 and up of the register are unchanged

Run on AMD Zen 5 (EPYC 9645): 5 cases.

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
AESDECLAST xmm, xmm/m128
xmmexplicitread, write
xmm/m128explicitread

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
SSE_TYPE_4

Attributes

What else XED records about the forms. How to read.

Memory forms
aligned memory operand

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to AESDECLAST, each with the form it compiles to and the Clang options it needs. The forms come from compiling every intrinsic and decoding the result with Intel XED; all intrinsics A–Z explains the method.

IntrinsicCompiles to
_mm_aesdeclast_si128 __m128i _mm_aesdeclast_si128(__m128i __V, __m128i __R)

AESDECLAST xmm, xmm Legacy -maes

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
AES

AES
CPUID.01H:ECX[25] AES

Westmere, Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Silvermont, Goldmont, Goldmont Plus, Tremont, Snow Ridge, Lakefield, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, K10 (Family 10h), Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6

Note: Intel's manuals list AES-NI for Silvermont, as XED does; GCC's -march=silvermont leaves it out, and Intel's product pages show some of its Celeron parts without it.

Note: XED's AMD_K10 inherits everything from its Westmere chip, including SSSE3, SSE4.1, SSE4.2, AES-NI and PCLMULQDQ; GCC's -march=amdfam10 has none of them.

More AES-NI 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. The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s -march feature sets and AMD’s Processor Programming References, which the page of each processor cites.
  3. Clang's x86 intrinsic headers, LLVM 23.1.2 (commit 85ac56026243): the intrinsics, their signatures and doc comments, and the Clang of that release, which compiled each of them.
  4. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-39 (AESDECLAST)
  5. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  6. Software Optimization Guide for the AMD Zen5 Microarchitecture (58455, rev. 1.00, August 2024), Wayback Machine copy of AMD's ZIP

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 intrinsics and their signatures come from Clang, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.