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

VEXPANDPS spreads consecutive singles from the low end of a register, or from memory, over the destination elements whose mask bits are set, in order; the other elements keep their values or, with {z}, become zero. It is VPEXPANDD for float data: the same operation on 32-bit elements, with the same encodings apart from the opcode, and that page describes the memory form, which reads only as many elements as the mask selects, and the usual loop around it. VCOMPRESSPS is the reverse.

Bits, not numbers

Although its name says singles, VEXPANDPS does no arithmetic. It raises no SIMD floating-point exception, ignores MXCSR, and moves NaNs, denormals and negative zeros bit for bit, as a move does. Its operation on this site is therefore written on doublewords. The difference from VPEXPANDD lies only in which instruction a compiler chooses: the intrinsics on __m512 give VEXPANDPS, those on __m512i VPEXPANDD.

What compilers do with it

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 emit it for the intrinsics _mm512_mask_expand_ps, _mm512_maskz_expand_ps and the expandloadu forms, and neither produces it from a C loop that hands out consecutive values to selected positions. With a constant mask they simplify:

  • With all bits set, an expansion is a plain copy, and both compilers drop the instruction.
  • With only the low eight bits set, the first eight elements stay where they are and the rest become zero, which is a zeroing masked move: GCC emits vmovaps zmm0{k1}{z}, zmm0, and Clang vmovaps ymm0, ymm0, whose VEX encoding clears everything above bit 255.
  • Any other constant, such as 5555h, keeps VEXPANDPS with the mask loaded into a mask register.

Recorded on Zen 5

In the cases recorded on Zen 5, the memory form with merging placed the first doublewords of the buffer, in order, in the selected elements and left the others alone, and an XMM memory form whose mask selected none of the four elements gave zero with {z}.

AMD’s Zen 5 guide lists VEXPANDPS as two macro-ops with a latency of 2, 4 and 5 cycles for XMM, YMM and ZMM, the same as VPEXPANDD.

In the optimization guide

What the optimization guide says about VEXPANDPS, 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

Every encoding of VEXPANDPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VEXPANDPS zmm {k}{z}, m512 VEXPANDPS_ZMMf32_MASKmskw_MEMf32_AVX512EVEX.512.66.0F38.W0 88 /rAVX10.1 or AVX512F
VEXPANDPS zmm {k}{z}, zmm VEXPANDPS_ZMMf32_MASKmskw_ZMMf32_AVX512EVEX.512.66.0F38.W0 88 /rAVX10.1 or AVX512F
VEXPANDPS xmm {k}{z}, m128 VEXPANDPS_XMMf32_MASKmskw_MEMf32_AVX512EVEX.128.66.0F38.W0 88 /rAVX10.1 or AVX512F + AVX512VL
VEXPANDPS xmm {k}{z}, xmm VEXPANDPS_XMMf32_MASKmskw_XMMf32_AVX512EVEX.128.66.0F38.W0 88 /rAVX10.1 or AVX512F + AVX512VL
VEXPANDPS ymm {k}{z}, m256 VEXPANDPS_YMMf32_MASKmskw_MEMf32_AVX512EVEX.256.66.0F38.W0 88 /rAVX10.1 or AVX512F + AVX512VL
VEXPANDPS ymm {k}{z}, ymm VEXPANDPS_YMMf32_MASKmskw_YMMf32_AVX512EVEX.256.66.0F38.W0 88 /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.51FP1 FP21 / 0.51FP1 FP28 / 0.5FP1 FP2
  1. Zen 4 model, xmm form: AMD's spreadsheets give latency 2 for Zen 4 and Zen 5 (AMD 57647, row 1130; AMD 58455, row 686).

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 singles 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}

VEXPANDPS with merging, {k1}With merging: result singles 15 to 0: unchanged, a7, a6, unchanged, a5, unchanged, unchanged, a4, a3, unchanged, a2, unchanged, unchanged, a1, a0, unchanged.0123456789101112131415zmm2or m512a1111111100000000k1a0a1a2a3a4a5a6a7zmm1

zeroing, {k1}{z}

VEXPANDPS with zeroing, {k1}{z}With zeroing: result singles 15 to 0: 0, a7, a6, 0, a5, 0, 0, a4, a3, 0, a2, 0, 0, a1, a0, 0.00000000

Example mask k1 = 0x69A6. Shown for the zmm form; the xmm and ymm forms work the same on 4 and 8 singles. A memory source is read only as far as the elements it gives.

With merging: result singles 15 to 0: unchanged, a7, a6, unchanged, a5, unchanged, unchanged, a4, a3, unchanged, a2, unchanged, unchanged, a1, a0, unchanged.

With zeroing: result singles 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 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
VEXPANDPS xmm {k}{z}, xmm/m128 VEXPANDPS ymm {k}{z}, ymm/m256 VEXPANDPS 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 VEXPANDPS, 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_ps __m128 _mm_mask_expand_ps(__m128 __W, __mmask8 __U, __m128 __A)

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

_mm_mask_expandloadu_ps __m128 _mm_mask_expandloadu_ps(__m128 __W, __mmask8 __U, const void *__P)

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

_mm_maskz_expand_ps __m128 _mm_maskz_expand_ps(__mmask8 __U, __m128 __A)

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

_mm_maskz_expandloadu_ps __m128 _mm_maskz_expandloadu_ps(__mmask8 __U, const void *__P)

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

_mm256_mask_expand_ps __m256 _mm256_mask_expand_ps(__m256 __W, __mmask8 __U, __m256 __A)

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

_mm256_mask_expandloadu_ps __m256 _mm256_mask_expandloadu_ps(__m256 __W, __mmask8 __U, const void *__P)

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

_mm256_maskz_expand_ps __m256 _mm256_maskz_expand_ps(__mmask8 __U, __m256 __A)

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

_mm256_maskz_expandloadu_ps __m256 _mm256_maskz_expandloadu_ps(__mmask8 __U, const void *__P)

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

_mm512_mask_expand_ps __m512 _mm512_mask_expand_ps(__m512 __W, __mmask16 __U, __m512 __A)

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

_mm512_mask_expandloadu_ps __m512 _mm512_mask_expandloadu_ps(__m512 __W, __mmask16 __U, const void *__P)

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

_mm512_maskz_expand_ps __m512 _mm512_maskz_expand_ps(__mmask16 __U, __m512 __A)

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

_mm512_maskz_expandloadu_ps __m512 _mm512_maskz_expandloadu_ps(__mmask16 __U, const void *__P)

VEXPANDPS 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-166 (VEXPANDPS)
  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.