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

VBLENDMPS builds each single of its destination from one of two sources, chosen by a mask register: the second source where the mask bit is set, the first where it is clear, or zero there with {z}. It is VPBLENDMD under a floating-point name, the same selection on doublewords, and its page sets it against masked moves. It copies bits and does no arithmetic: the SDM lists no floating-point exception, and MXCSR stayed at 1F80h in all 6 cases recorded on Zen 5. The mask is typically written by VCMPPS, where the VEX form VBLENDVPS takes the sign bits of a compare result held in a vector register.

Recorded on Zen 5

vblendmps zmm1{k2}, zmm2, dword bcst [mem] put the memory single into the nine elements where F2C9h, the low 16 bits of K2, has a bit set, and kept ZMM2’s in the other seven. At 128 bits only bits 3:0 count: vblendmps xmm0{k2}{z}, xmm31, dword bcst [mem] wrote the broadcast value to elements 0 and 3, by 9h, and zeros elsewhere.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 treat _mm512_mask_blend_ps as the integer blends: a masked VMOVAPS or VMOVUPS when they can, VBLENDMPS when the result must land in the other register. For o[i] = a[i] > b[i] ? c[i] : 5.0f over float arrays both emit VCMPPS into a mask and VBLENDMPS with c[i] from memory, where -march=x86-64-v3 gives VCMPPS into a vector and VBLENDVPS. A leaky ReLU, a[i] > 0 ? a[i] : 0.01f * a[i], splits them: GCC multiplies only the elements that need it, zero-masked, and blends with VBLENDMPS; Clang multiplies all and merges a[i] back with a masked VMOVAPS.

AMD’s Zen 5 latency spreadsheet gives VBLENDMPS one cycle and four per cycle on any of the four vector pipes, as VPBLENDMD.

Forms

Every encoding of VBLENDMPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VBLENDMPS zmm {k}{z}, zmm, zmm VBLENDMPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512EVEX.512.66.0F38.W0 65 /rAVX10.1 or AVX512F
VBLENDMPS zmm {k}{z}, zmm, m512/m32bcst VBLENDMPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512EVEX.512.66.0F38.W0 65 /rAVX10.1 or AVX512F
VBLENDMPS xmm {k}{z}, xmm, xmm VBLENDMPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.128.66.0F38.W0 65 /rAVX10.1 or AVX512F + AVX512VL
VBLENDMPS xmm {k}{z}, xmm, m128/m32bcst VBLENDMPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.128.66.0F38.W0 65 /rAVX10.1 or AVX512F + AVX512VL
VBLENDMPS ymm {k}{z}, ymm, ymm VBLENDMPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512EVEX.256.66.0F38.W0 65 /rAVX10.1 or AVX512F + AVX512VL
VBLENDMPS ymm {k}{z}, ymm, m256/m32bcst VBLENDMPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512EVEX.256.66.0F38.W0 65 /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}, zmm, zmmzmm {k}{z}, zmm, m512/m32bcstxmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
xmm {k}{z}, xmm, m128/m32bcstymm {k}{z}, ymm, m256/m32bcst
Skylake-SP, Ice Lake2 / 0.67p0158 / 0.5p0151 / 0.33p0157 / 0.5p0158 / 0.5p015
Sapphire Rapids1 / 0.5p059 / 0.5p051 / 0.33p0158 / 0.33p0159 / 0.33p015
Zen 41 / 1FP0 FP18 / 1FP0 FP11 / 0.51FP0 FP18 / 0.5FP0 FP18 / 0.5FP0 FP1
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.25 for Zen 4 and Zen 5 (AMD 57647, row 891; AMD 58455, row 434).

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.

Blend by mask: each single comes from xmm3 where its bit of k1 is 1; elsewhere merging takes it from xmm2, and zeroing writes 0.

merging, {k1}

VBLENDMPS with merging, {k1}With merging: result singles 3 to 0: b3, a2, b1, b0.0132xmm2a1110k1b0b1b3a2xmm10132xmm3or m128b

zeroing, {k1}{z}

VBLENDMPS with zeroing, {k1}{z}With zeroing: result singles 3 to 0: b3, 0, b1, b0.01231110k1b0b1b30xmm10132xmm3or m128b

Example mask k1 = 0x0B. Every single of the wider forms works alike. With m32bcst, one single from memory stands for every element of xmm3.

With merging: result singles 3 to 0: b3, a2, b1, b0.

With zeroing: result singles 3 to 0: b3, 0, b1, b0.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

for i in range(VL // 32):
    if k1[i]:
        zmm1.d[i] = src3.d[i]
    elif zeroing:
        zmm1.d[i] = 0
    else:
        zmm1.d[i] = zmm2.d[i]
# m32bcst: src3.f32[i] is the m32 for every i
# 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
VBLENDMPS xmm {k}{z}, xmm, xmm/m128/m32bcst VBLENDMPS ymm {k}{z}, ymm, ymm/m256/m32bcst VBLENDMPS zmm {k}{z}, zmm, zmm/m512/m32bcst
xmm, ymm, zmmexplicitwrite
{k}explicitread (selector)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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
opmask selects the source
Memory forms
embedded broadcast (tuple Full); memory fault suppression

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. LLVM 23.1.2's x86 scheduling models (commit 85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them.
  4. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  5. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-9 (VBLENDMPD/VBLENDMPS)
  6. 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 timings come from LLVM's scheduling models, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.