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

VPBLENDMW builds each word 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 word form of VPBLENDMD, whose page sets it against masked moves and the older blends, and needs AVX512BW. Words have no broadcast form, so the second source is a register or a full vector in memory.

Recorded on Zen 5

  • The first source is the fallback. vpblendmw zmm17{k1}, zmm30, zmm2 took ZMM2’s word where K1 had a bit set and ZMM30’s elsewhere; none of the old ZMM17 survived, although the mask is written as merging.
  • Zeroing. vpblendmw ymm17{k2}{z}, ymm30, ymm2 took YMM2’s words at the bits set in F2C9h, the low 16 bits of K2, and wrote 0 to the other seven words.
  • No mask copies the second source: {evex} vpblendmw ymm5, ymm5, ymmword ptr [mem] loaded memory.

In compiled code

_mm512_mask_blend_epi16(k, a, b) takes b where k is set. GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 compile it to vmovdqu16 zmm0{k1}, zmm1 when the result may replace a, and with b in memory to a masked load; with the operands the other way round they emit VPBLENDMW. In loops over short arrays the two compilers differ. For o[i] = a[i] ? 7 : o[i], GCC marks the zero elements with VPCMPW and blends a vector of sevens with o read straight from memory by VPBLENDMW, while Clang marks the nonzero ones with VPTESTMW and writes sevens with a masked VMOVDQU16 store, leaving the rest of o untouched. For o[i] = a[i] > b[i] ? c[i] : b[i] both load b and overwrite it with a masked VMOVDQU16 load of c.

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

Forms

Every encoding of VPBLENDMW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPBLENDMW xmm {k}{z}, xmm, xmm VPBLENDMW_XMMu16_MASKmskw_XMMu16_XMMu16_AVX512EVEX.128.66.0F38.W1 66 /rAVX10.1 or AVX512BW + AVX512VL
VPBLENDMW xmm {k}{z}, xmm, m128 VPBLENDMW_XMMu16_MASKmskw_XMMu16_MEMu16_AVX512EVEX.128.66.0F38.W1 66 /rAVX10.1 or AVX512BW + AVX512VL
VPBLENDMW ymm {k}{z}, ymm, ymm VPBLENDMW_YMMu16_MASKmskw_YMMu16_YMMu16_AVX512EVEX.256.66.0F38.W1 66 /rAVX10.1 or AVX512BW + AVX512VL
VPBLENDMW ymm {k}{z}, ymm, m256 VPBLENDMW_YMMu16_MASKmskw_YMMu16_MEMu16_AVX512EVEX.256.66.0F38.W1 66 /rAVX10.1 or AVX512BW + AVX512VL
VPBLENDMW zmm {k}{z}, zmm, zmm VPBLENDMW_ZMMu16_MASKmskw_ZMMu16_ZMMu16_AVX512EVEX.512.66.0F38.W1 66 /rAVX10.1 or AVX512BW
VPBLENDMW zmm {k}{z}, zmm, m512 VPBLENDMW_ZMMu16_MASKmskw_ZMMu16_MEMu16_AVX512EVEX.512.66.0F38.W1 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 1989; AMD 58455, row 440).

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

merging, {k1}

VPBLENDMW with merging, {k1}With merging: result words 7 to 0: b7, a6, b5, b4, a3, a2, b1, a0.02361457xmm2a11110000k1a0a2a3a6b1b4b5b7xmm102361457xmm3or m128b

zeroing, {k1}{z}

VPBLENDMW with zeroing, {k1}{z}With zeroing: result words 7 to 0: b7, 0, b5, b4, 0, 0, b1, 0.0123456711110000k10000b1b4b5b7xmm102361457xmm3or m128b

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

With merging: result words 7 to 0: b7, a6, b5, b4, a3, a2, b1, a0.

With zeroing: result words 7 to 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 // 16):
    if k1[i]:
        zmm1.w[i] = src3.w[i]
    elif zeroing:
        zmm1.w[i] = 0
    else:
        zmm1.w[i] = zmm2.w[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
VPBLENDMW xmm {k}{z}, xmm, xmm/m128 VPBLENDMW ymm {k}{z}, ymm, ymm/m256 VPBLENDMW 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.