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

VMOVDQU32 is one of the four EVEX encodings of the unaligned integer move: a load, store or register copy of 16, 32 or 64 bytes at any address, as VMOVDQU is in VEX, with a write mask that selects doublewords. Unmasked, it moves the same bits as VMOVDQU8, VMOVDQU16 and VMOVDQU64. The VMOVDQU8 page covers masked loads and stores, whose left-out elements raise no fault, and their use at the end of a buffer. What the doubleword form brings:

  • AVX512F alone. VMOVDQU32 and VMOVDQU64 need only AVX512F (or AVX10.1); the byte and word forms need AVX512BW. A loop over int elements can mask its tail on any AVX-512 processor.
  • A 16-bit mask for 512 bits. One mask bit per int, so a tail of n elements takes the n low bits of a 16-bit mask. On Zen 5, vmovdqu32 xmm7{k2}{z}, [mem] with 1001b in the low bits of K2 loaded doublewords 0 and 3 and zeroed 1 and 2 and the rest of ZMM7.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 compile a tail written with intrinsics, _mm512_maskz_loadu_epi32 and _mm512_mask_storeu_epi32 under a mask made by BZHI of FFFFh and KMOVD, to vmovdqu32 zmm0{k1}{z}, [rsi] and vmovdqu32 [rdi]{k1}, zmm0. Neither masks the tail of a plain C loop at -O2: GCC leaves a loop of unknown count scalar, and Clang finishes one with scalar code.

Unmasked, the element size is only a name, and the compilers differ. GCC loads and stores the zmm registers of a vectorized int loop with VMOVDQU32, a[i] = b[i] + c[i] for example, but compiles _mm512_loadu_si512 to VMOVDQU64. Clang stays with ymm registers and VEX VMOVDQU in the loop, and uses VMOVUPS for the 512-bit intrinsic.

For _mm512_mask_blend_epi32, a merging register copy, both emit the aligned name VMOVDQA32. Zen 5’s 9 recorded cases cover every form, masked, at all three widths, all at an aligned address.

Forms

Every encoding of VMOVDQU32 that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMOVDQU32 zmm {k}{z}, zmm VMOVDQU32_ZMMu32_MASKmskw_ZMMu32_AVX512EVEX.512.F3.0F.W0 6F /r
EVEX.512.F3.0F.W0 7F /r
AVX10.1 or AVX512F
VMOVDQU32 zmm {k}{z}, m512 VMOVDQU32_ZMMu32_MASKmskw_MEMu32_AVX512EVEX.512.F3.0F.W0 6F /rAVX10.1 or AVX512F
VMOVDQU32 m512 {k}, zmm VMOVDQU32_MEMu32_MASKmskw_ZMMu32_AVX512EVEX.512.F3.0F.W0 7F /rAVX10.1 or AVX512F
VMOVDQU32 xmm {k}{z}, xmm VMOVDQU32_XMMu32_MASKmskw_XMMu32_AVX512EVEX.128.F3.0F.W0 6F /r
EVEX.128.F3.0F.W0 7F /r
AVX10.1 or AVX512F + AVX512VL
VMOVDQU32 xmm {k}{z}, m128 VMOVDQU32_XMMu32_MASKmskw_MEMu32_AVX512EVEX.128.F3.0F.W0 6F /rAVX10.1 or AVX512F + AVX512VL
VMOVDQU32 m128 {k}, xmm VMOVDQU32_MEMu32_MASKmskw_XMMu32_AVX512EVEX.128.F3.0F.W0 7F /rAVX10.1 or AVX512F + AVX512VL
VMOVDQU32 ymm {k}{z}, ymm VMOVDQU32_YMMu32_MASKmskw_YMMu32_AVX512EVEX.256.F3.0F.W0 6F /r
EVEX.256.F3.0F.W0 7F /r
AVX10.1 or AVX512F + AVX512VL
VMOVDQU32 ymm {k}{z}, m256 VMOVDQU32_YMMu32_MASKmskw_MEMu32_AVX512EVEX.256.F3.0F.W0 6F /rAVX10.1 or AVX512F + AVX512VL
VMOVDQU32 m256 {k}, ymm VMOVDQU32_MEMu32_MASKmskw_YMMu32_AVX512EVEX.256.F3.0F.W0 7F /rAVX10.1 or AVX512F + AVX512VL

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.
Modelzmm {k}{z}, zmmno maskzmm {k}{z}, zmmwith a mask, zeroingzmm {k}{z}, m512no mask
ymm {k}{z}, m256no mask
zmm {k}{z}, m512with a mask, zeroingm512 {k}, zmm
m128 {k}, xmm
m256 {k}, ymm
xmm {k}{z}, xmmno mask
ymm {k}{z}, ymmno mask
xmm {k}{z}, xmmwith a mask, zeroing
ymm {k}{z}, ymmwith a mask, zeroing
xmm {k}{z}, m128no maskxmm {k}{z}, m128with a mask, zeroingymm {k}{z}, m256with a mask, zeroing
Skylake-SP1 / 0.5p051 / 0.5p058 / 0.5p0158 / 0.5p0151 / 1p23471 / 0.33p0151 / 0.33p0157 / 0.5p0157 / 0.5p0158 / 0.5p015
Ice Lake1 / 0.5p051 / 0.5p058 / 0.5p0158 / 0.5p0151 / 0.5p47891 / 0.33p0151 / 0.33p0157 / 0.5p0157 / 0.5p0158 / 0.5p015
Sapphire Rapids1 / 01 / 0.5p058 / 0.33p2 p3 p109 / 0.5p0512 / 0.5p47891 / 01 / 0.33p0157 / 0.33p2 p3 p108 / 0.33p0159 / 0.33p015
Zen 40 / 0.170 / 0.178 / 0.5FP45 LSU Load8 / 0.5FP45 LSU Load1 / 1FP45 FPSt LSU Store0 / 0.170 / 0.178 / 0.5FP45 LSU Load8 / 0.5FP45 LSU Load8 / 0.5FP45 LSU Load

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.

A masked move: each doubleword is copied where its bit of k1 is 1; elsewhere merging keeps the old element, and zeroing writes 0.VMOVDQU32 xmm {k}{z}, xmm/m128 VMOVDQU32 ymm {k}{z}, ymm/m256 VMOVDQU32 zmm {k}{z}, zmm/m512

merging, {k1}

VMOVDQU32 with merging, {k1}With merging: result doublewords 3 to 0: a3, unchanged, a1, a0.0123xmm2or m128a1110k1a0a1a3xmm1

zeroing, {k1}{z}

VMOVDQU32 with zeroing, {k1}{z}With zeroing: result doublewords 3 to 0: a3, 0, a1, a0.0

Example mask k1 = 0x0B. Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms.

With merging: result doublewords 3 to 0: a3, unchanged, a1, a0.

With zeroing: result doublewords 3 to 0: a3, 0, a1, a0.

A masked store: each doubleword is copied where its bit of k1 is 1; elsewhere the memory is left as it was.VMOVDQU32 m128 {k}, xmm VMOVDQU32 m256 {k}, ymm VMOVDQU32 m512 {k}, zmm
VMOVDQU32 with merging, {k1}Memory doublewords 3 to 0: a3, unchanged, a1, a0.xmm2am128

Example mask k1 = 0x0B. Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms.

Memory doublewords 3 to 0: a3, unchanged, a1, a0.

Operation

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

VMOVDQU32 xmm {k}{z}, xmm/m128 VMOVDQU32 ymm {k}{z}, ymm/m256 VMOVDQU32 zmm {k}{z}, zmm/m512
for i in range(VL // 32):
    if k1[i]:
        zmm1.d[i] = src2.d[i]
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# zmm1 is zeroed from bit VL up

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

VMOVDQU32 m128 {k}, xmm VMOVDQU32 m256 {k}, ymm VMOVDQU32 m512 {k}, zmm
for i in range(VL // 32):
    if k1[i]:
        mem.d[i] = zmm2.d[i]
    # else: mem.d[i] is not written

Run on AMD Zen 5 (EPYC 9645): 3 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
VMOVDQU32 xmm {k}{z}, xmm/m128 VMOVDQU32 ymm {k}{z}, ymm/m256 VMOVDQU32 zmm {k}{z}, zmm/m512
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128, ymm/m256, zmm/m512explicitread
VMOVDQU32 m128 {k}, xmm VMOVDQU32 m256 {k}, ymm VMOVDQU32 m512 {k}, zmm
m128/256/512explicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread

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
AVX512-E4

Attributes

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

All forms
write masking
Memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VMOVDQU32, 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_mask_loadu_epi32 __m128i _mm_mask_loadu_epi32(__m128i __W, __mmask8 __U, const void *__P)

VMOVDQU32 xmm {k}, m128 EVEX.128 -mavx512vl

_mm_mask_storeu_epi32 void _mm_mask_storeu_epi32(void *__P, __mmask8 __U, __m128i __A)

VMOVDQU32 m128 {k}, xmm EVEX.128 -mavx512vl

_mm_maskz_loadu_epi32 __m128i _mm_maskz_loadu_epi32(__mmask8 __U, const void *__P)

VMOVDQU32 xmm {k}{z}, m128 EVEX.128 -mavx512vl

_mm256_mask_loadu_epi32 __m256i _mm256_mask_loadu_epi32(__m256i __W, __mmask8 __U, const void *__P)

VMOVDQU32 ymm {k}, m256 EVEX.256 -mavx512vl

_mm256_mask_storeu_epi32 void _mm256_mask_storeu_epi32(void *__P, __mmask8 __U, __m256i __A)

VMOVDQU32 m256 {k}, ymm EVEX.256 -mavx512vl

_mm256_maskz_loadu_epi32 __m256i _mm256_maskz_loadu_epi32(__mmask8 __U, const void *__P)

VMOVDQU32 ymm {k}{z}, m256 EVEX.256 -mavx512vl

_mm512_loadu_epi32 __m512i _mm512_loadu_epi32(const void *__P)

VMOVDQU32 zmm, m512 EVEX.512 -mavx512fClang emits the equivalent VMOVDQU64

_mm512_storeu_epi32 void _mm512_storeu_epi32(void *__P, __m512i __A)

VMOVDQU32 m512, zmm EVEX.512 -mavx512fClang emits the equivalent VMOVDQU64

_mm512_mask_loadu_epi32 __m512i _mm512_mask_loadu_epi32(__m512i __W, __mmask16 __U, const void *__P)

VMOVDQU32 zmm {k}, m512 EVEX.512 -mavx512f

_mm512_mask_storeu_epi32 void _mm512_mask_storeu_epi32(void *__P, __mmask16 __U, __m512i __A)

VMOVDQU32 m512 {k}, zmm EVEX.512 -mavx512f

_mm512_maskz_loadu_epi32 __m512i _mm512_maskz_loadu_epi32(__mmask16 __U, const void *__P)

VMOVDQU32 zmm {k}{z}, m512 EVEX.512 -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
AVX512F_512

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
AVX512F_128

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

or

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

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, Zen 4, Zen 5, Zen 6
AVX512F_256
Same as AVX512F_128Same as AVX512F_128

More AVX10.1 instructions

All 686 AVX10.1 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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-64 (MOVDQU,VMOVDQU8/16/32/64)

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.