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}, zmm31 with 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}, ymm30 with 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

Every encoding of VPEXPANDQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPEXPANDQ zmm {k}{z}, m512 VPEXPANDQ_ZMMu64_MASKmskw_MEMu64_AVX512EVEX.512.66.0F38.W1 89 /rAVX10.1 or AVX512F
VPEXPANDQ zmm {k}{z}, zmm VPEXPANDQ_ZMMu64_MASKmskw_ZMMu64_AVX512EVEX.512.66.0F38.W1 89 /rAVX10.1 or AVX512F
VPEXPANDQ xmm {k}{z}, m128 VPEXPANDQ_XMMu64_MASKmskw_MEMu64_AVX512EVEX.128.66.0F38.W1 89 /rAVX10.1 or AVX512F + AVX512VL
VPEXPANDQ xmm {k}{z}, xmm VPEXPANDQ_XMMu64_MASKmskw_XMMu64_AVX512EVEX.128.66.0F38.W1 89 /rAVX10.1 or AVX512F + AVX512VL
VPEXPANDQ ymm {k}{z}, m256 VPEXPANDQ_YMMu64_MASKmskw_MEMu64_AVX512EVEX.256.66.0F38.W1 89 /rAVX10.1 or AVX512F + AVX512VL
VPEXPANDQ ymm {k}{z}, ymm VPEXPANDQ_YMMu64_MASKmskw_YMMu64_AVX512EVEX.256.66.0F38.W1 89 /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}, m512
ymm {k}{z}, m256
zmm {k}{z}, zmmno mask
xmm {k}{z}, xmmno mask
ymm {k}{z}, ymmno mask
zmm {k}{z}, zmmwith a mask, zeroing
xmm {k}{z}, xmmwith a mask, zeroing
ymm {k}{z}, ymmwith a mask, zeroing
xmm {k}{z}, m128
Skylake-SP, Ice Lake11 / 2p54 / 2p54 / 2p510 / 2p5
Sapphire Rapids11 / 2p53 / 2p56 / 2p510 / 2p5
Zen 48 / 0.5FP1 FP21 / 0.5FP1 FP21 / 0.5FP1 FP28 / 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.

Expand: the low quadwords of zmm2, in order, go to the places whose bit of k1 is 1; elsewhere merging keeps the old element, and zeroing writes 0.

merging, {k1}

VPEXPANDQ with merging, {k1}With merging: result quadwords 7 to 0: a3, unchanged, a2, unchanged, unchanged, a1, a0, unchanged.01234567zmm2or m512a11110000k1a0a1a2a3zmm1

zeroing, {k1}{z}

VPEXPANDQ with zeroing, {k1}{z}With zeroing: result quadwords 7 to 0: a3, 0, a2, 0, 0, a1, a0, 0.0000

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 up

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

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.

IntrinsicCompiles to
_mm_mask_expand_epi64 __m128i _mm_mask_expand_epi64(__m128i __W, __mmask8 __U, __m128i __A)

VPEXPANDQ xmm {k}, xmm EVEX.128 -mavx512vl

_mm_mask_expandloadu_epi64 __m128i _mm_mask_expandloadu_epi64(__m128i __W, __mmask8 __U, const void *__P)

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

_mm_maskz_expand_epi64 __m128i _mm_maskz_expand_epi64(__mmask8 __U, __m128i __A)

VPEXPANDQ xmm {k}{z}, xmm EVEX.128 -mavx512vl

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

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

_mm256_mask_expand_epi64 __m256i _mm256_mask_expand_epi64(__m256i __W, __mmask8 __U, __m256i __A)

VPEXPANDQ ymm {k}, ymm EVEX.256 -mavx512vl

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

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

_mm256_maskz_expand_epi64 __m256i _mm256_maskz_expand_epi64(__mmask8 __U, __m256i __A)

VPEXPANDQ ymm {k}{z}, ymm EVEX.256 -mavx512vl

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

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

_mm512_mask_expand_epi64 __m512i _mm512_mask_expand_epi64(__m512i __W, __mmask8 __U, __m512i __A)

VPEXPANDQ zmm {k}, zmm EVEX.512 -mavx512f

_mm512_mask_expandloadu_epi64 __m512i _mm512_mask_expandloadu_epi64(__m512i __W, __mmask8 __U, const void *__P)

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

_mm512_maskz_expand_epi64 __m512i _mm512_maskz_expand_epi64(__mmask8 __U, __m512i __A)

VPEXPANDQ zmm {k}{z}, zmm EVEX.512 -mavx512f

_mm512_maskz_expandloadu_epi64 __m512i _mm512_maskz_expandloadu_epi64(__mmask8 __U, const void *__P)

VPEXPANDQ 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 2C, page 5-546 (VPEXPANDQ)
  7. 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.