Extensions
Forms
11 (4 VEX, 7 EVEX)
Data
Intel XED v2026.08.23

VMOVD is the VEX and EVEX form of MOVD, whose page covers the 32-bit copies compilers make with it. Into an XMM register the newer encodings zero every bit above 31, where the legacy form keeps bits 128 and up. Only a 128-bit form exists: VEX.L = 1 or a VEX.vvvv other than 1111b raises #UD in both vendors’ manuals, and so does an EVEX.vvvv other than 1111b (AMD’s in its table of illegal EVEX encodings, Section 3.2.4). The VEX form needs AVX, the EVEX form AVX-512F or AVX10.1, which reaches XMM16 to XMM31 but takes no mask. With W1 the same opcodes are VMOVQ.

On Zen 5, the recorded vmovd xmm12, dword ptr [mem] cleared bits 511:32 of ZMM12, and {evex} vmovd dword ptr [mem], xmm5 wrote four bytes and left the next ones alone.

A copy between vector registers

AVX10.2 adds the form the older encodings lack, VMOVD from XMM to XMM, which keeps the low doubleword and zeroes the rest. It reuses VMOVQ’s register-copy opcodes, F3 0F 7E and 66 0F D6, with EVEX.W0 where VMOVQ has W1. Zen 5 has no AVX10.2, so these forms were not run.

In compiled code

In our builds at -O2 with -march=x86-64-v3 or x86-64-v4, GCC 14 and Clang 23 emit VMOVD where MOVD’s page shows MOVD. The zeroing makes a zero-extended vector free: for _mm256_zextsi128_si256(_mm_cvtsi32_si128(x)) Clang emits only vmovd xmm0, edi, while GCC adds a vmovdqa xmm0, xmm0 that changes nothing. Keeping only element 0 of four ints, v & (v4si){-1, 0, 0, 0}, takes Clang a VXORPS and a VBLENDPS at -v4, and with -mavx10.2 added the single vmovd xmm0, xmm0.

AMD’s latency spreadsheet for Zen 5 lists VMOVD from a general-purpose register as one macro-op in its VEX and EVEX rows, where legacy MOVD takes two. Only the EVEX rows give latencies: 1 cycle for a move out of the XMM register, on FP4 or FP5, and 0 for a move into it.

Forms

Every encoding of VMOVD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMOVD xmm, m32 VMOVD_XMMdq_MEMdVEX.128.66.0F.W0 6E /rAVX
VMOVD m32, xmm VMOVD_MEMd_XMMdVEX.128.66.0F.W0 7E /rAVX
VMOVD xmm, r32 VMOVD_XMMdq_GPR32dVEX.128.66.0F.W0 6E /rAVX
VMOVD r32, xmm VMOVD_GPR32d_XMMdVEX.128.66.0F.W0 7E /rAVX
VMOVD xmm, r32 VMOVD_XMMu32_GPR32u32_AVX512EVEX.128.66.0F.W0 6E /rAVX10.1 or AVX512F
VMOVD xmm, m32 VMOVD_XMMu32_MEMu32_AVX512EVEX.128.66.0F.W0 6E /rAVX10.1 or AVX512F
VMOVD r32, xmm VMOVD_GPR32u32_XMMu32_AVX512EVEX.128.66.0F.W0 7E /rAVX10.1 or AVX512F
VMOVD m32, xmm VMOVD_MEMu32_XMMu32_AVX512EVEX.128.66.0F.W0 7E /rAVX10.1 or AVX512F
VMOVD xmm, xmm VMOVD_XMMu32_XMMu32_AVX512_MOVZXCEVEX.128.F3.0F.W0 7E /r
EVEX.128.66.0F.W0 D6 /r
AVX10.2
VMOVD xmm, m32 VMOVD_XMMu32_MEMu32_AVX512_MOVZXCEVEX.128.F3.0F.W0 7E /rAVX10.2
VMOVD m32, xmm VMOVD_MEMu32_XMMu32_AVX512_MOVZXCEVEX.128.66.0F.W0 D6 /rAVX10.2

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.
Modelxmm, m32m32, xmmxmm, r32r32, xmmxmm, m32
Sandy Bridge6 / 0.5p231 / 1p4 p231 / 1p52 / 1p0
Haswell, Broadwell5 / 0.5p231 / 1p23471 / 1p51 / 1p0
Skylake5 / 0.5p231 / 1p23471 / 1p52 / 1p0
Skylake-SP5 / 0.5p231 / 1p23471 / 1p52 / 1p06 / 0.5p015
Ice Lake5 / 0.5p231 / 0.5p47891 / 1p52 / 1p06 / 0.5p015
Alder Lake7 / 0.33p2 p3 p1012 / 0.5p47893 / 1p53 / 1p0
Sapphire Rapids7 / 0.33p2 p3 p1012 / 0.5p47893 / 1p53 / 1p07 / 0.33p2 p3 p10
Lunar Lake6 / 0.33p20 p21 p2212 / 0.5p10 p11 p25 p26 p273 / 0.33p1353 / 0.5V0 V1
Piledriver5 / 1.5FPMAL FPU0 FPU12 / 1.5AGLU01 FPSTO FPU2 FPU3 Store11 / 1FPFMA FPU0 FPU111 / 1EX0 FPFMA FPU0
Zen8 / 0.5AGU0 AGU11 / 0.5AGU0 AGU13 / 1FPU22 / 1FPU2
Zen 28 / 0.33AGU0 AGU1 AGU21 / 0.33AGU0 AGU1 AGU23 / 1FPU22 / 1FPU2
Zen 38 / 0.5FP45 LSU Load1 / 1FP45 FPSt LSU Store1 / 1FP451 / 1FP45
Zen 48 / 0.5FP45 LSU Load1 / 1FP45 FPSt LSU Store1 / 1FP451 / 1FP458 / 0.5FP45 LSU Load
Jaguar5 / 1FPU0 FPU1 VALU0 VALU12 / 1FPU18 / 0.5FPA FPM FPU0 FPU14 / 1ALU0 FPA FPU0

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.

The doubleword in r32 goes to the low end of xmm1, and the rest of xmm1 is zeroed.VMOVD xmm, r/m32
VMOVD: the low elementResult doublewords 3 to 0: 0, 0, 0, a0.0r32or m32aa0000xmm1

Result doublewords 3 to 0: 0, 0, 0, a0.

The low doubleword of xmm2 goes to m32.VMOVD r/m32, xmm
VMOVD: the low elementm32 receives doubleword 0 of xmm2: a0.123xmm2am32

m32 receives doubleword 0 of xmm2: a0.

The low doubleword of xmm2 goes to the low end of xmm1, and the rest of xmm1 is zeroed.VMOVD xmm, xmm
VMOVD: the low elementResult doublewords 3 to 0: 0, 0, 0, a0.

Result doublewords 3 to 0: 0, 0, 0, a0.

Operation

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

VMOVD xmm, r/m32
xmm1.write(src2.d[0])  # zeroed from bit 32 up

Run on AMD Zen 5 (EPYC 9645): 4 cases. The AVX10.2 forms were not run: none of these processors has AVX10.2.

VMOVD r/m32, xmm
dest.write(xmm2.d[0])  # a register: bits 63:32 cleared

Run on AMD Zen 5 (EPYC 9645): 4 cases. The AVX10.2 forms were not run: none of these processors has AVX10.2.

VMOVD xmm, xmm
xmm1.write(xmm2.d[0])  # zeroed from bit 32 up

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

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
VMOVD xmm, r/m32 VMOVD xmm, xmm/m32
xmmexplicitwrite
r/m32, xmm/m32explicitread
VMOVD r/m32, xmm
r/m32explicitwrite
xmmexplicitread

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.

VEX forms
avx-type-5
EVEX forms
AVX512-E9NF

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VMOVD, 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_cvtsi128_si32 int _mm_cvtsi128_si32(__m128i __a)

VMOVD r32, xmm VEX.128 -mavxwith AVX enabled

_mm_cvtsi32_si128 __m128i _mm_cvtsi32_si128(int __a)

VMOVD xmm, r32 VEX.128 -mavxwith AVX enabled

_mm_loadu_si32 __m128i _mm_loadu_si32(const void *__a)

VMOVD xmm, m32 VEX.128 -mavxwith AVX enabled

_mm_move_epi32 __m128i _mm_move_epi32(__m128i __A)

VMOVD xmm, xmm EVEX.128 -mavx10.2

_mm_storeu_si32 void _mm_storeu_si32(void *__p, __m128i __b)

VMOVD m32, xmm VEX.128 -mavxwith AVX enabled

_mm512_cvtsi512_si32 int _mm512_cvtsi512_si32(__m512i __A)

VMOVD r32, xmm VEX.128 -mavx512f

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
AVX

AVX
CPUID.01H:ECX[28] AVX

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, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX512F_128N

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512_MOVZXC_128

AVX10.2
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 2 AVX10 version

Nova Lake, Diamond Rapids

More AVX instructions

All 253 AVX instructions

More AVX10.1 instructions

All 686 AVX10.1 instructions

More AVX10.2 instructions

All 96 AVX10.2 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-54 (MOVD/MOVQ)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit, 256-Bit, and 512-Bit Media Instructions (26568, rev. 3.27, July 2026)
  9. 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.