Instruction
VPEXPANDW
Spreads consecutive words 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
VPEXPANDW takes consecutive words from the low end of its source and
places them, in order, at the destination words whose mask bits are
set; the other words keep their values, or become zero with {z}. It
is the word form of VPEXPANDD, whose page explains
the operation and the unpacking loop around it, and came with
VPEXPANDB in AVX512_VBMI2, which x86-64-v4 lacks
and -march=znver5 enables. A ZMM register holds 32 words, so the mask
is the low 32 bits of a mask register; from memory, only as many words
are read as the mask has bits set. VPCOMPRESSW
does the reverse.
Recorded on Zen 5
- Zeroing. With mask bits 0, 1, 3, 5, 6 and 7 set,
vpexpandw xmm17{k3}{z}, xmmword ptr [...]placed the first six words of memory at those words and cleared words 2 and 4. - Merging, in place. In
vpexpandw xmm5{k4}, xmm5, with mask bits 0, 2, 5, 6 and 7, words 0 to 4 of XMM5 moved to those places, while words 1, 3 and 4 kept their old values: the words came from the source as it was before the instruction.
In compiled code
GCC 14 and Clang 23 at -O2 with -march=znver5 emit VPEXPANDW only
for the intrinsics: _mm512_maskz_expandloadu_epi16(k, p) is one
vpexpandw zmm0{k1}{z}, zmmword ptr [rsi], after a KMOVD of the mask in
Clang. Neither vectorizes d[i] = keep[i] ? c[j++] : 0 over
uint16_t arrays.
AMD’s Zen 5 latency spreadsheet gives the same rows as for VPEXPANDB: two macro-ops, each on pipe FP1 or FP2, 2, 4 and 5 cycles for the XMM, YMM and ZMM forms. It lists the word and byte forms under AVX512F, though the SDM places them in AVX512_VBMI2.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPEXPANDW xmm {k}{z}, m128
VPEXPANDW_XMMu16_MASKmskw_MEMu16_AVX512 | EVEX.128.66.0F38.W1 62 /r | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPEXPANDW xmm {k}{z}, xmm
VPEXPANDW_XMMu16_MASKmskw_XMMu16_AVX512 | EVEX.128.66.0F38.W1 62 /r | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPEXPANDW ymm {k}{z}, m256
VPEXPANDW_YMMu16_MASKmskw_MEMu16_AVX512 | EVEX.256.66.0F38.W1 62 /r | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPEXPANDW ymm {k}{z}, ymm
VPEXPANDW_YMMu16_MASKmskw_YMMu16_AVX512 | EVEX.256.66.0F38.W1 62 /r | AVX10.1 or AVX512_VBMI2 + AVX512VL |
VPEXPANDW zmm {k}{z}, m512
VPEXPANDW_ZMMu16_MASKmskw_MEMu16_AVX512 | EVEX.512.66.0F38.W1 62 /r | AVX10.1 or AVX512_VBMI2 |
VPEXPANDW zmm {k}{z}, zmm
VPEXPANDW_ZMMu16_MASKmskw_ZMMu16_AVX512 | EVEX.512.66.0F38.W1 62 /r | AVX10.1 or AVX512_VBMI2 |
Latency and throughput
| Model | xmm {k}{z}, m128no mask | xmm {k}{z}, m128with a mask, zeroingymm {k}{z}, m256with a mask, zeroingzmm {k}{z}, m512with a mask, zeroing | xmm {k}{z}, xmmno mask | xmm {k}{z}, xmmwith a mask, zeroing | ymm {k}{z}, m256no maskzmm {k}{z}, m512no mask | ymm {k}{z}, ymmno mask | ymm {k}{z}, ymmwith a mask, zeroing | zmm {k}{z}, zmmno mask | zmm {k}{z}, zmmwith a mask, zeroing |
|---|---|---|---|---|---|---|---|---|---|
| Ice Lake | 10 / 1p5 | 10 / 1p5 | 3 / 1p5 | 3 / 1p5 | 10 / 1p5 | 3 / 1p5 | 3 / 1p5 | 3 / 1p5 | 3 / 1p5 |
| Sapphire Rapids | 10 / 2p5 | 13 / 2p5 | 3 / 2p5 | 8 / 2p5 | 11 / 2p5 | 3 / 2p5 | 8 / 2p5 | 3 / 2p5 | 8 / 2p5 |
| Zen 4 | 8 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 1 / 0.5FP1 FP2 | 8 / 0.5FP1 FP2 | 4 / 1FP1 FP2 | 4 / 1FP1 FP2 | 5 / 1FP1 FP2 | 5 / 1FP1 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 ymm form; the xmm and zmm forms work the same on 8 and 32 words. A memory source is read only as far as the elements it gives.
With merging: result words 15 to 0: unchanged, a7, a6, unchanged, a5, unchanged, unchanged, a4, a3, unchanged, a2, unchanged, unchanged, a1, a0, unchanged.
With zeroing: result words 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 // 16):
if k1[i]:
zmm1.w[i] = src2.w[j]
j += 1
elif zeroing:
zmm1.w[i] = 0
# else: zmm1.w[i] keeps its value
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPEXPANDW xmm {k}{z}, xmm/m128 VPEXPANDW ymm {k}{z}, ymm/m256 VPEXPANDW 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 VPEXPANDW, 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_epi16
__m128i _mm_mask_expand_epi16(__m128i __S, __mmask8 __U, __m128i __D) |
|
_mm_mask_expandloadu_epi16
__m128i _mm_mask_expandloadu_epi16(__m128i __S, __mmask8 __U, const void *__P) |
|
_mm_maskz_expand_epi16
__m128i _mm_maskz_expand_epi16(__mmask8 __U, __m128i __D) |
|
_mm_maskz_expandloadu_epi16
__m128i _mm_maskz_expandloadu_epi16(__mmask8 __U, const void *__P) |
|
_mm256_mask_expand_epi16
__m256i _mm256_mask_expand_epi16(__m256i __S, __mmask16 __U, __m256i __D) |
|
_mm256_mask_expandloadu_epi16
__m256i _mm256_mask_expandloadu_epi16(__m256i __S, __mmask16 __U, const void *__P) |
|
_mm256_maskz_expand_epi16
__m256i _mm256_maskz_expand_epi16(__mmask16 __U, __m256i __D) |
|
_mm256_maskz_expandloadu_epi16
__m256i _mm256_maskz_expandloadu_epi16(__mmask16 __U, const void *__P) |
|
_mm512_mask_expand_epi16
__m512i _mm512_mask_expand_epi16(__m512i __S, __mmask32 __U, __m512i __D) |
|
_mm512_mask_expandloadu_epi16
__m512i _mm512_mask_expandloadu_epi16(__m512i __S, __mmask32 __U, const void *__P) |
|
_mm512_maskz_expand_epi16
__m512i _mm512_maskz_expand_epi16(__mmask32 __U, __m512i __D) |
|
_mm512_maskz_expandloadu_epi16
__m512i _mm512_maskz_expandloadu_epi16(__mmask32 __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 |
|---|---|---|
AVX512_VBMI2_128 | AVX10.1 or AVX512_VBMI2 + AVX512VL | Ice Lake (client), Tiger Lake, Nova Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6 |
AVX512_VBMI2_256 | Same as AVX512_VBMI2_128 | Same as AVX512_VBMI2_128 |
AVX512_VBMI2_512 | AVX10.1 or AVX512_VBMI2 | Same as AVX512_VBMI2_128 |
More AVX10.1 instructions
- VPERMI2D
- VPERMI2PD
- VPERMI2PS
- VPERMI2Q
- VPERMI2W
- VPERMILPD
- VPERMILPS
- VPERMPD
- VPERMPS
- VPERMQ
- VPERMT2B
- VPERMT2D
- VPERMT2PD
- VPERMT2PS
- VPERMT2Q
- VPERMT2W
- VPERMW
- VPEXPANDB
- VPEXPANDD
- VPEXPANDQ
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPGATHERDD
- VPGATHERDQ
- VPGATHERQD
- VPGATHERQQ
- VPINSRB
- VPINSRD
- VPINSRQ
- VPINSRW
- VPLZCNTD
- VPLZCNTQ
- VPMADD52HUQ
- VPMADD52LUQ
- VPMADDUBSW
- VPMADDWD
- VPMAXSB
- VPMAXSD
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-541 (VPEXPANDB/
VPEXPANDW) - 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.