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

VPBLENDMB builds each byte 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 the byte form of VPBLENDMD, whose page sets it against masked moves and the older blends, and needs AVX512BW. One bit per byte makes the mask as wide as the vector has bytes, 16, 32 or 64 bits, so a ZMM blend reads the whole mask register (filled with KMOVQ). As for VPBLENDMW, there is no broadcast form.

Recorded on Zen 5

  • All 64 bits. In vpblendmb zmm0{k4}, zmm31, zmmword ptr [mem] K4 held 4E432F055A6A6DE5h: its low byte, E5h, took byte 0 from memory and byte 1 from ZMM31, and its high byte, 4Eh, took bytes 57 to 59 and 62 from memory.
  • One register three times. vpblendmb zmm5{k6}, zmm5, zmm5 left ZMM5 as it was. With {z}, vpblendmb ymm5{k2}{z}, ymm5, ymm5 acted as a zero-masked move: it cleared the 12 bytes whose bits are clear in FCB6F2C9h, the low 32 bits of K2, and bits 256 and up.
  • No mask copies the second source: {evex} vpblendmb ymm0, ymm31, ymmword ptr [mem] loaded memory.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 compile _mm512_mask_blend_epi8 as they do the word form: a masked VMOVDQU8 when the result may replace the first operand or the second is in memory, VPBLENDMB otherwise. For o[i] = a[i] > b[i] ? c[i] : 5 over uint8_t arrays, both compare with VPCMPUB, which Clang prints as VPCMPNLEUB, and blend a vector of fives with c[i] read from memory by VPBLENDMB. With -march=x86-64-v3 there is no unsigned byte compare: GCC builds a selector vector with VPSUBUSB and VPCMPEQB, Clang with VPMINUB and VPCMPEQB, and both blend with VPBLENDVB, which takes the top bit of each selector byte.

AMD’s Zen 5 latency spreadsheet gives VPBLENDMB one cycle and four per cycle on any of the four vector pipes, as VPBLENDMD. The 6 recorded cases cover the register and memory forms at all three widths.

Forms

Every encoding of VPBLENDMB that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPBLENDMB xmm {k}{z}, xmm, xmm VPBLENDMB_XMMu8_MASKmskw_XMMu8_XMMu8_AVX512EVEX.128.66.0F38.W0 66 /rAVX10.1 or AVX512BW + AVX512VL
VPBLENDMB xmm {k}{z}, xmm, m128 VPBLENDMB_XMMu8_MASKmskw_XMMu8_MEMu8_AVX512EVEX.128.66.0F38.W0 66 /rAVX10.1 or AVX512BW + AVX512VL
VPBLENDMB ymm {k}{z}, ymm, ymm VPBLENDMB_YMMu8_MASKmskw_YMMu8_YMMu8_AVX512EVEX.256.66.0F38.W0 66 /rAVX10.1 or AVX512BW + AVX512VL
VPBLENDMB ymm {k}{z}, ymm, m256 VPBLENDMB_YMMu8_MASKmskw_YMMu8_MEMu8_AVX512EVEX.256.66.0F38.W0 66 /rAVX10.1 or AVX512BW + AVX512VL
VPBLENDMB zmm {k}{z}, zmm, zmm VPBLENDMB_ZMMu8_MASKmskw_ZMMu8_ZMMu8_AVX512EVEX.512.66.0F38.W0 66 /rAVX10.1 or AVX512BW
VPBLENDMB zmm {k}{z}, zmm, m512 VPBLENDMB_ZMMu8_MASKmskw_ZMMu8_MEMu8_AVX512EVEX.512.66.0F38.W0 66 /rAVX10.1 or AVX512BW

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.
Modelxmm {k}{z}, xmm, xmmno mask
ymm {k}{z}, ymm, ymmno mask
xmm {k}{z}, xmm, xmmwith a mask, zeroing
ymm {k}{z}, ymm, ymmwith a mask, zeroing
xmm {k}{z}, xmm, m128no maskxmm {k}{z}, xmm, m128with a mask, zeroingymm {k}{z}, ymm, m256no maskymm {k}{z}, ymm, m256with a mask, zeroingzmm {k}{z}, zmm, zmmno maskzmm {k}{z}, zmm, zmmwith a mask, zeroingzmm {k}{z}, zmm, m512no maskzmm {k}{z}, zmm, m512with a mask, zeroing
Skylake-SP, Ice Lake1 / 0.33p0151 / 0.33p0157 / 0.5p0157 / 0.5p0158 / 0.5p0158 / 0.5p0152 / 0.5p052 / 0.5p058 / 0.5p0158 / 0.5p015
Sapphire Rapids1 / 0.33p0153 / 0.33p0158 / 0.33p01511 / 0.33p0159 / 0.33p01511 / 0.33p0151 / 0.5p053 / 0.5p059 / 0.5p0511 / 0.5p05
Zen 41 / 0.51FP0 FP31 / 0.51FP0 FP38 / 0.5FP0 FP38 / 0.5FP0 FP38 / 0.5FP0 FP38 / 0.5FP0 FP31 / 1FP0 FP31 / 1FP0 FP38 / 1FP0 FP38 / 1FP0 FP3
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.25 for Zen 4 and Zen 5 (AMD 57647, row 1980; AMD 58455, row 439).

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

merging, {k1}

VPBLENDMB with merging, {k1}With merging: result bytes 15 to 0: a15, a14, a13, a12, a11, a10, a9, a8, b7, a6, b5, b4, a3, a2, b1, a0.0236891011121314151457xmm2a1111000000000000k1a0a2a3a6a8a9a10a11a12a13a14a15b1b4b5b7xmm10236891011121314151457xmm3or m128b

zeroing, {k1}{z}

VPBLENDMB with zeroing, {k1}{z}With zeroing: result bytes 15 to 0: 0, 0, 0, 0, 0, 0, 0, 0, b7, 0, b5, b4, 0, 0, b1, 0.01234567891011121314151111000000000000k1000000000000b1b4b5b7xmm10236891011121314151457xmm3or m128b

Example mask k1 = 0xB2. Every byte of the wider forms works alike.

With merging: result bytes 15 to 0: a15, a14, a13, a12, a11, a10, a9, a8, b7, a6, b5, b4, a3, a2, b1, a0.

With zeroing: result bytes 15 to 0: 0, 0, 0, 0, 0, 0, 0, 0, b7, 0, b5, b4, 0, 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 // 8):
    if k1[i]:
        zmm1.b[i] = src3.b[i]
    elif zeroing:
        zmm1.b[i] = 0
    else:
        zmm1.b[i] = zmm2.b[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
VPBLENDMB xmm {k}{z}, xmm, xmm/m128 VPBLENDMB ymm {k}{z}, ymm, ymm/m256 VPBLENDMB zmm {k}{z}, zmm, zmm/m512
xmm, ymm, zmmexplicitwrite
{k}explicitread (selector)
xmm, ymm, zmmexplicitread
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
opmask selects the source
Memory forms
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
AVX512BW_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512BW + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW
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
AVX512BW_256
Same as AVX512BW_128Same as AVX512BW_128
AVX512BW_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512BW
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW

Same as AVX512BW_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-437 (VPBLENDMB/VPBLENDMW)
  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.