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

VBLENDMPD builds each double 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 VBLENDMPS on 64-bit elements, and the same selection as VPBLENDMQ; like both it copies bits, raises no floating-point exception and reads at most the low 8 bits of the mask. Compiled code uses it as it uses VBLENDMPS: GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 blend a select with a constant fallback, o[i] = a[i] > b[i] ? c[i] : 5.0 over double arrays, with VCMPPD and VBLENDMPD, where -march=x86-64-v3 gives VBLENDVPD.

Recorded on Zen 5

vblendmpd ymm17{k4}{z}, ymm30, ymm2 read only bits 3:0 of K4, 5h: it took elements 0 and 2 from YMM2 and wrote zero to elements 1 and 3 and to bits 256 and up. Without a mask, {evex} vblendmpd xmm14, xmm8, xmm29 copied XMM29. MXCSR stayed at 1F80h in all 6 cases.

Patching special lanes

Intel’s optimization manual uses it in a division with 52 good bits (Section 17.25.4, Example 17-41). VRCP14PD estimates the reciprocal of each divisor and FMAs refine it, but for a divisor of zero or infinity the estimate is already exact, infinity or zero, and the refinement would spoil it. VFPCLASSPD marks those lanes, VBLENDMPD restores the estimate there, and the last FMA runs under the inverted mask.

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

Forms

Every encoding of VBLENDMPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VBLENDMPD zmm {k}{z}, zmm, zmm VBLENDMPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F38.W1 65 /rAVX10.1 or AVX512F
VBLENDMPD zmm {k}{z}, zmm, m512/m64bcst VBLENDMPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F38.W1 65 /rAVX10.1 or AVX512F
VBLENDMPD xmm {k}{z}, xmm, xmm VBLENDMPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F38.W1 65 /rAVX10.1 or AVX512F + AVX512VL
VBLENDMPD xmm {k}{z}, xmm, m128/m64bcst VBLENDMPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F38.W1 65 /rAVX10.1 or AVX512F + AVX512VL
VBLENDMPD ymm {k}{z}, ymm, ymm VBLENDMPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F38.W1 65 /rAVX10.1 or AVX512F + AVX512VL
VBLENDMPD ymm {k}{z}, ymm, m256/m64bcst VBLENDMPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F38.W1 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/m64bcstxmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
xmm {k}{z}, xmm, m128/m64bcstymm {k}{z}, ymm, m256/m64bcst
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 886; AMD 58455, row 433).

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 double comes from xmm3 where its bit of k1 is 1; elsewhere merging takes it from xmm2, and zeroing writes 0.

merging, {k1}

VBLENDMPD with merging, {k1}With merging: result doubles 1 to 0: b1, a0.01xmm2a10k1a0b1xmm101xmm3or m128b

zeroing, {k1}{z}

VBLENDMPD with zeroing, {k1}{z}With zeroing: result doubles 1 to 0: b1, 0.0110k10b1xmm101xmm3or m128b

Example mask k1 = 0x02. Every double of the wider forms works alike. With m64bcst, one double from memory stands for every element of xmm3.

With merging: result doubles 1 to 0: b1, a0.

With zeroing: result doubles 1 to 0: b1, 0.

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 // 64):
    if k1[i]:
        zmm1.q[i] = src3.q[i]
    elif zeroing:
        zmm1.q[i] = 0
    else:
        zmm1.q[i] = zmm2.q[i]
# m64bcst: src3.f64[i] is the m64 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
VBLENDMPD xmm {k}{z}, xmm, xmm/m128/m64bcst VBLENDMPD ymm {k}{z}, ymm, ymm/m256/m64bcst VBLENDMPD zmm {k}{z}, zmm, zmm/m512/m64bcst
xmm, ymm, zmmexplicitwrite
{k}explicitread (selector)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  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 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.