Instruction
VPEXPANDD
Spreads consecutive doublewords from the low end of a register or from memory to the positions selected by a mask.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPEXPANDD is the reverse of VPCOMPRESSD: it takes
consecutive doublewords from the low end of its source and spreads
them, in order, over the destination elements whose mask bits are set.
With mask bits 1, 2 and 5 set, elements 0, 1 and 2 of the source land
in elements 1, 2 and 5. The other elements keep their old values, or
become zero with {z}. Without a mask it is a plain copy.
The memory form
From memory, VPEXPANDD reads only as many elements as the mask has set bits, one after another from the address, and nothing above them. A read that stops at the end of a buffer cannot fault on the page beyond, so a loop can take the next few values from a packed stream without padding it. The 8-bit displacement of this form counts in elements of 4 bytes, not in whole vectors as for most EVEX loads, which matters only to someone encoding it by hand.
Unpacking a stream
The usual pattern is a mask from a compare, an unaligned load at a running position in the packed data, VPEXPANDD, and POPCNT of the mask, moved over with KMOVW or KMOVD, to advance the position. Intel’s optimization manual times it on a loop that gives each positive element the next value from the array (Section 17.6.1, Example 17-14): VPEXPANDD runs 8.58 times as fast as scalar code, against 4.23 for AVX2, which needs a table of 256 VPERMD index vectors and a VMASKMOVPS store. The same manual expands sparse matrices for AMX with the byte form, VPEXPANDB, one 64-bit mask per row (Section 20.18, Example 20-31).
GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 emit VPEXPANDD for
the intrinsics, _mm512_maskz_expand_epi32 for the register form and
_mm512_maskz_expandloadu_epi32 for the memory form, each with a
merging mask variant, but neither vectorizes the manual’s loop: both
keep it scalar.
AMD’s Zen 5 guide lists VPEXPANDD as two macro-ops with a latency of 2, 4 and 5 cycles for XMM, YMM and ZMM, from a register or memory alike, while it marks the memory form of VPCOMPRESSD as microcoded. VPEXPANDQ expands quadwords, VEXPANDPS singles, and AVX512_VBMI2’s VPEXPANDB and VPEXPANDW bytes and words.
In the optimization guide
What the optimization guide says about VPEXPANDD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Vectors
- Shuffles and lane crossing: VPCOMPRESSD and VPEXPANDD replace shuffle tables, but compressing straight to memory is microcode on Zen 4 and Zen 5.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPEXPANDD zmm {k}{z}, m512
VPEXPANDD_ZMMu32_MASKmskw_MEMu32_AVX512 | EVEX.512.66.0F38.W0 89 /r | AVX10.1 or AVX512F |
VPEXPANDD zmm {k}{z}, zmm
VPEXPANDD_ZMMu32_MASKmskw_ZMMu32_AVX512 | EVEX.512.66.0F38.W0 89 /r | AVX10.1 or AVX512F |
VPEXPANDD xmm {k}{z}, m128
VPEXPANDD_XMMu32_MASKmskw_MEMu32_AVX512 | EVEX.128.66.0F38.W0 89 /r | AVX10.1 or AVX512F + AVX512VL |
VPEXPANDD xmm {k}{z}, xmm
VPEXPANDD_XMMu32_MASKmskw_XMMu32_AVX512 | EVEX.128.66.0F38.W0 89 /r | AVX10.1 or AVX512F + AVX512VL |
VPEXPANDD ymm {k}{z}, m256
VPEXPANDD_YMMu32_MASKmskw_MEMu32_AVX512 | EVEX.256.66.0F38.W0 89 /r | AVX10.1 or AVX512F + AVX512VL |
VPEXPANDD ymm {k}{z}, ymm
VPEXPANDD_YMMu32_MASKmskw_YMMu32_AVX512 | EVEX.256.66.0F38.W0 89 /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, m512ymm {k}{z}, m256 | zmm {k}{z}, zmmno maskxmm {k}{z}, xmmno maskymm {k}{z}, ymmno mask | zmm {k}{z}, zmmwith a mask, zeroingxmm {k}{z}, xmmwith a mask, zeroingymm {k}{z}, ymmwith a mask, zeroing | xmm {k}{z}, m128 |
|---|---|---|---|---|
| Skylake-SP, Ice Lake | 11 / 2p5 | 4 / 2p5 | 4 / 2p5 | 10 / 2p5 |
| Sapphire Rapids | 11 / 2p5 | 3 / 2p5 | 6 / 2p5 | 10 / 2p5 |
| Zen 4 | 8 / 0.5FP1 FP2 | 1 / 0.51FP1 FP2 | 1 / 0.51FP1 FP2 | 8 / 0.5FP1 FP2 |
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.
merging, {k1}
zeroing, {k1}{z}
Example mask k1 = 0x69A6. Shown for the zmm form; the xmm and ymm forms work the same on 4 and 8 doublewords. A memory source is read only as far as the elements it gives.
With merging: result doublewords 15 to 0: unchanged, a7, a6, unchanged, a5, unchanged, unchanged, a4, a3, unchanged, a2, unchanged, unchanged, a1, a0, unchanged.
With zeroing: result doublewords 15 to 0: 0, a7, a6, 0, a5, 0, 0, a4, a3, 0, a2, 0, 0, a1, a0, 0.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
j = 0
for i in range(VL // 32):
if k1[i]:
zmm1.d[i] = src2.d[j]
j += 1
elif zeroing:
zmm1.d[i] = 0
# else: zmm1.d[i] keeps its value
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPEXPANDD xmm {k}{z}, xmm/m128 VPEXPANDD ymm {k}{z}, ymm/m256 VPEXPANDD zmm {k}{z}, zmm/m512 | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm/m128, ymm/m256, zmm/m512 | explicit | read |
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 VPEXPANDD, 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.
| Intrinsic | Compiles to |
|---|---|
_mm_mask_expand_epi32
__m128i _mm_mask_expand_epi32(__m128i __W, __mmask8 __U, __m128i __A) |
|
_mm_mask_expandloadu_epi32
__m128i _mm_mask_expandloadu_epi32(__m128i __W, __mmask8 __U, const void *__P) |
|
_mm_maskz_expand_epi32
__m128i _mm_maskz_expand_epi32(__mmask8 __U, __m128i __A) |
|
_mm_maskz_expandloadu_epi32
__m128i _mm_maskz_expandloadu_epi32(__mmask8 __U, const void *__P) |
|
_mm256_mask_expand_epi32
__m256i _mm256_mask_expand_epi32(__m256i __W, __mmask8 __U, __m256i __A) |
|
_mm256_mask_expandloadu_epi32
__m256i _mm256_mask_expandloadu_epi32(__m256i __W, __mmask8 __U, const void *__P) |
|
_mm256_maskz_expand_epi32
__m256i _mm256_maskz_expand_epi32(__mmask8 __U, __m256i __A) |
|
_mm256_maskz_expandloadu_epi32
__m256i _mm256_maskz_expandloadu_epi32(__mmask8 __U, const void *__P) |
|
_mm512_mask_expand_epi32
__m512i _mm512_mask_expand_epi32(__m512i __W, __mmask16 __U, __m512i __A) |
|
_mm512_mask_expandloadu_epi32
__m512i _mm512_mask_expandloadu_epi32(__m512i __W, __mmask16 __U, const void *__P) |
|
_mm512_maskz_expand_epi32
__m512i _mm512_maskz_expand_epi32(__mmask16 __U, __m512i __A) |
|
_mm512_maskz_expandloadu_epi32
__m512i _mm512_maskz_expandloadu_epi32(__mmask16 __U, const void *__P) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512F_512 | AVX10.1 or 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 or AVX512F + 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_128 | Same as AVX512F_128 |
More AVX10.1 instructions
- VPERMD
- VPERMI2B
- VPERMI2D
- VPERMI2PD
- VPERMI2PS
- VPERMI2Q
- VPERMI2W
- VPERMILPD
- VPERMILPS
- VPERMPD
- VPERMPS
- VPERMQ
- VPERMT2B
- VPERMT2D
- VPERMT2PD
- VPERMT2PS
- VPERMT2Q
- VPERMT2W
- VPERMW
- VPEXPANDB
- VPEXPANDQ
- VPEXPANDW
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPGATHERDD
- VPGATHERDQ
- VPGATHERQD
- VPGATHERQQ
- VPINSRB
- VPINSRD
- VPINSRQ
- VPINSRW
- VPLZCNTD
- VPLZCNTQ
- VPMADD52HUQ
- VPMADD52LUQ
- VPMADDUBSW
- VPMADDWD
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-544 (VPEXPANDD)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
- 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.