Instruction
VPEXPANDQ
Spreads consecutive quadwords 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
VPEXPANDQ takes consecutive quadwords from the low end of its source,
a register or memory, and spreads them in order over the destination
elements whose mask bits are set; the others keep their values or, with
{z}, become zero. It is VPEXPANDD on 64-bit
elements, 2, 4 or 8 of them, and that page describes the memory form,
which reads only the selected count of elements, and the loops it
serves. VPCOMPRESSQ is the reverse, and
VEXPANDPD the same operation under a floating-point
name. It came with AVX512F, and AVX512_VBMI2 added the byte and word
forms, VPEXPANDB and
VPEXPANDW.
Recorded on Zen 5
- Two of eight.
vpexpandq zmm0{k1}, zmm31with mask bits 5 and 7 set put quadwords 0 and 1 of ZMM31 in elements 5 and 7 and left the other six elements of ZMM0 alone. - Zeroing.
vpexpandq ymm17{k2}{z}, ymm30with mask bits 0 and 3 set gave quadword 0 in element 0, quadword 1 in element 3 and zero elsewhere.
In compiled code
At -O2 with -march=x86-64-v4, GCC 14 and Clang 23 emit VPEXPANDQ for
_mm512_maskz_expandloadu_epi64, straight from memory, and for
_mm256_mask_expand_epi64 on YMM registers. With the constant mask FFh
on a ZMM register the expansion is a copy, and both drop it.
AMD’s Zen 5 latency spreadsheet gives two macro-ops on pipes FP1 or FP2 and latencies of 2, 4 and 5 cycles for XMM, YMM and ZMM.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPEXPANDQ zmm {k}{z}, m512
VPEXPANDQ_ZMMu64_MASKmskw_MEMu64_AVX512 | EVEX.512.66.0F38.W1 89 /r | AVX10.1 or AVX512F |
VPEXPANDQ zmm {k}{z}, zmm
VPEXPANDQ_ZMMu64_MASKmskw_ZMMu64_AVX512 | EVEX.512.66.0F38.W1 89 /r | AVX10.1 or AVX512F |
VPEXPANDQ xmm {k}{z}, m128
VPEXPANDQ_XMMu64_MASKmskw_MEMu64_AVX512 | EVEX.128.66.0F38.W1 89 /r | AVX10.1 or AVX512F + AVX512VL |
VPEXPANDQ xmm {k}{z}, xmm
VPEXPANDQ_XMMu64_MASKmskw_XMMu64_AVX512 | EVEX.128.66.0F38.W1 89 /r | AVX10.1 or AVX512F + AVX512VL |
VPEXPANDQ ymm {k}{z}, m256
VPEXPANDQ_YMMu64_MASKmskw_MEMu64_AVX512 | EVEX.256.66.0F38.W1 89 /r | AVX10.1 or AVX512F + AVX512VL |
VPEXPANDQ ymm {k}{z}, ymm
VPEXPANDQ_YMMu64_MASKmskw_YMMu64_AVX512 | EVEX.256.66.0F38.W1 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.5FP1 FP2 | 1 / 0.5FP1 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 = 0xA6. Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 quadwords. A memory source is read only as far as the elements it gives.
With merging: result quadwords 7 to 0: a3, unchanged, a2, unchanged, unchanged, a1, a0, unchanged.
With zeroing: result quadwords 7 to 0: 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 // 64):
if k1[i]:
zmm1.q[i] = src2.q[j]
j += 1
elif zeroing:
zmm1.q[i] = 0
# else: zmm1.q[i] keeps its value
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPEXPANDQ xmm {k}{z}, xmm/m128 VPEXPANDQ ymm {k}{z}, ymm/m256 VPEXPANDQ 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 VPEXPANDQ, 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_epi64
__m128i _mm_mask_expand_epi64(__m128i __W, __mmask8 __U, __m128i __A) |
|
_mm_mask_expandloadu_epi64
__m128i _mm_mask_expandloadu_epi64(__m128i __W, __mmask8 __U, const void *__P) |
|
_mm_maskz_expand_epi64
__m128i _mm_maskz_expand_epi64(__mmask8 __U, __m128i __A) |
|
_mm_maskz_expandloadu_epi64
__m128i _mm_maskz_expandloadu_epi64(__mmask8 __U, const void *__P) |
|
_mm256_mask_expand_epi64
__m256i _mm256_mask_expand_epi64(__m256i __W, __mmask8 __U, __m256i __A) |
|
_mm256_mask_expandloadu_epi64
__m256i _mm256_mask_expandloadu_epi64(__m256i __W, __mmask8 __U, const void *__P) |
|
_mm256_maskz_expand_epi64
__m256i _mm256_maskz_expand_epi64(__mmask8 __U, __m256i __A) |
|
_mm256_maskz_expandloadu_epi64
__m256i _mm256_maskz_expandloadu_epi64(__mmask8 __U, const void *__P) |
|
_mm512_mask_expand_epi64
__m512i _mm512_mask_expand_epi64(__m512i __W, __mmask8 __U, __m512i __A) |
|
_mm512_mask_expandloadu_epi64
__m512i _mm512_mask_expandloadu_epi64(__m512i __W, __mmask8 __U, const void *__P) |
|
_mm512_maskz_expand_epi64
__m512i _mm512_maskz_expand_epi64(__mmask8 __U, __m512i __A) |
|
_mm512_maskz_expandloadu_epi64
__m512i _mm512_maskz_expandloadu_epi64(__mmask8 __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
- VPERMI2B
- VPERMI2D
- VPERMI2PD
- VPERMI2PS
- VPERMI2Q
- VPERMI2W
- VPERMILPD
- VPERMILPS
- VPERMPD
- VPERMPS
- VPERMQ
- VPERMT2B
- VPERMT2D
- VPERMT2PD
- VPERMT2PS
- VPERMT2Q
- VPERMT2W
- VPERMW
- VPEXPANDB
- VPEXPANDD
- VPEXPANDW
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPGATHERDD
- VPGATHERDQ
- VPGATHERQD
- VPGATHERQQ
- VPINSRB
- VPINSRD
- VPINSRQ
- VPINSRW
- VPLZCNTD
- VPLZCNTQ
- VPMADD52HUQ
- VPMADD52LUQ
- VPMADDUBSW
- VPMADDWD
- VPMAXSB
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-546 (VPEXPANDQ)
- 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.