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

MOVDIR64B copies 64 bytes from memory to memory. It reads the source, an ordinary memory operand of any alignment, perhaps in several pieces, and writes the destination, whose address is in a general-purpose register (an offset in ES), with one 64-byte write that is never split. The destination must be aligned to 64 bytes, or it raises #GP. Intel’s optimization manual (Section 3.12.1) notes that no other instruction guarantees an atomic write wider than 8 bytes.

A doorbell for devices

The write is a direct store, as MOVDIRI’s is: it follows the write-combining protocol whatever the destination’s memory type, uncacheable included, bypasses the caches and is never combined with later stores to the same address. That suits a device that takes a whole work descriptor through one memory-mapped register. Direct stores are weakly ordered, so a descriptor could reach the device before earlier writes it depends on; Intel’s manual recommends an SFENCE right before the direct store, and with _mm_sfence(); _movdir64b(portal, desc); GCC 14 and Clang 23 at -O2 (with -mmovdir64b) emit just that: SFENCE, then movdir64b rdi, zmmword ptr [rsi]. The manual adds that the descriptor itself, stored just before, needs no fence, since MOVDIR64B reads it from the same addresses, and that on Sapphire Rapids it is best aligned and written with 64-byte AVX-512 stores, so that the read can be forwarded from them.

ENQCMD shares the opcode bytes, 0F 38 F8, with an F2 prefix instead of 66. It writes 64 bytes the same way but replaces the first four with the thread’s PASID and a privilege bit, and reports in ZF whether the device accepted the command.

Address size, on Zen 5

The register is 64 bits wide in 64-bit mode, 32 with a 67H prefix. On Zen 5 with the prefix, RCX = 53184B0610000000H wrote to 10000000H, the upper half ignored, and a source of EBX + 20000000H with EBX = F0000040H wrapped to 10000040H. Destinations 8 and 32 bytes past a 64-byte boundary raised #GP and left memory alone.

Of AMD’s processors, the page lists Zen 5 and Zen 6 as having MOVDIR64B (CPUID leaf 7, ECX bit 28), and GCC 14 enables it for -march=znver5 but not znver4. AMD’s Zen 5 guide lists it, with MOVDIRI, as microcoded. APX adds an EVEX form; Zen 5 has no APX, so it was not run.

In the optimization guide

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

Golden Cove and Raptor Cove

  • Loads, stores and caches: Sapphire Rapids added MOVDIRI and MOVDIR64B, weakly ordered stores for ringing a device’s doorbell without stalling the stores behind them.

Tremont

Forms

Every encoding of MOVDIR64B that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
MOVDIR64B r16/32/64, m512 MOVDIR64B_GPRa_MEM66 0F 38 F8 /rMOVDIR64B
MOVDIR64B r16/32/64, m512 MOVDIR64B_GPRav_MEMu32_APXEVEX.LLZ.66.MAP4.SCALABLE F8 /rAPX_F + MOVDIR64B

Latency and throughput

What the scheduling models of LLVM 23.1.2 give for each form, not measurements: latency / reciprocal throughput in cycles, the ports under them. A row is a model, or models that agree; a dash, a form that its processors lack. Memory forms: latency from the address, ports without the load and store units. Which processors each model covers.
Modelr16, m512
Alder Lake, Sapphire Rapids1 / 0.5p06
Lunar Lake1 / 0.5p024

Operation

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

a = low(dest, ASIZE)             # the register holds the address: 64 bits
                                 # wide, 32 with 67h; ES, no override
if a % 64 != 0:
    fault(GP, 0)                 # it must be 64-byte aligned
v = src.read()                   # 64 bytes, maybe in several reads
store(a, 512, v)                 # one 64-byte direct store: around the
                                 # caches, weakly ordered, never split

Run on AMD Zen 5 (EPYC 9645): 10 cases. The APX forms were not run: 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
MOVDIR64B r16/32/64, m512
r16/32/64explicitread
m512explicitread
m512 at [operand 1]implicitwrite

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.

Legacy forms
none in XED
EVEX forms
APX-EVEX-INT

Attributes

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

All forms
aligned memory operand

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to MOVDIR64B, 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
_movdir64b void _movdir64b(void *__dst, const void *__src)

MOVDIR64B r16/32/64, m512 Legacy -mmovdir64b

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
MOVDIR64B

MOVDIR64B
CPUID.(EAX=07H,ECX=0):ECX[28] MOVDIR64B

Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Snow Ridge, Sierra Forest, Clearwater Forest, Zen 5, Zen 6
APX_F_MOVDIR64B

APX_F + MOVDIR64B
CPUID.(EAX=07H,ECX=1):EDX[21] APX_F
CPUID.(EAX=07H,ECX=0):ECX[28] MOVDIR64B

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. 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. LLVM 23.1.2's x86 scheduling models (commit 85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them.
  5. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-50 (MOVDIR64B)
  6. Intel Advanced Performance Extensions (Intel APX) Architecture Specification, revision 9.0 (355828-009, August 2026)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  8. 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 and the timings from LLVM's scheduling models, both part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.