Extensions
Forms
10 (4 VEX, 6 EVEX)
Data
Intel XED v2026.08.23

VPMADDWD multiplies signed words and adds each pair of neighboring products into a doubleword: the VEX and EVEX form of SSE2’s PMADDWD, whose page covers dot products and the one input that overflows, four words of 8000h. The newer forms write a separate destination, read memory at any alignment and zero the register above the vector length; since each pair stays inside its own doubleword, the wider registers simply hold more pairs. VEX.128 needs AVX and VEX.256 AVX2; the EVEX forms need AVX512BW (with AVX512VL below 512 bits) or AVX10.1 and add a write mask with one bit per doubleword result, but no broadcast. On Zen 5:

  • vpmaddwd xmm1, xmm2, xmm3 gave FFFFFFFFh, that is -1, for 7FFFh times 1 plus 8000h times 1, and 7FFF0001h for 8000h times 8000h plus 7FFFh times 7FFFh, the largest sum short of the overflow.
  • vpmaddwd ymm24{k7}{z}, ymm3, ymm3 wrote the five doublewords whose bits are set in E3h, the low byte of K7, and zeroed the other three.

Dot products in our builds

In our builds at -O2 over fixed-size int16_t arrays, s += a[i] * b[i] is VPMADDWD feeding VPADDD in GCC 14 and in Clang 23. GCC works on ymm registers with -march=x86-64-v3 and on zmm with -v4; Clang multiplies 16 bytes at a time at both levels and adds the results into ymm accumulators, and 32 bytes at a time with -march=znver5. With that option GCC uses VPDPWSSD instead, which folds the addition into the same instruction.

Written out by hand, d[i] = a[2*i] * b[2*i] + a[2*i+1] * b[2*i+1] is one VPMADDWD per vector in Clang. GCC first separates the even and odd words, with shifts and packs at -v3 and VPERMT2W at -v4, then multiplies them with VPMULLW and VPMULHW at -v3, or widens them with VPMOVSXWD and multiplies with VPMULLD at -v4, and adds the products. VPMULHW’s page shows Clang’s other use of it: full 32-bit products of words, each zero-extended so that it pairs with a zero.

AMD’s latency spreadsheet for Zen 5 gives the VEX row and the EVEX row alike a latency of 3 cycles, two per cycle on pipes FP0 and FP1.

Forms

Every encoding of VPMADDWD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPMADDWD xmm, xmm, m128 VPMADDWD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG F5 /rAVX
VPMADDWD xmm, xmm, xmm VPMADDWD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG F5 /rAVX
VPMADDWD ymm, ymm, m256 VPMADDWD_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG F5 /rAVX2
VPMADDWD ymm, ymm, ymm VPMADDWD_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG F5 /rAVX2
VPMADDWD xmm {k}{z}, xmm, xmm VPMADDWD_XMMi32_MASKmskw_XMMi16_XMMi16_AVX512EVEX.128.66.0F.WIG F5 /rAVX10.1 or AVX512BW + AVX512VL
VPMADDWD xmm {k}{z}, xmm, m128 VPMADDWD_XMMi32_MASKmskw_XMMi16_MEMi16_AVX512EVEX.128.66.0F.WIG F5 /rAVX10.1 or AVX512BW + AVX512VL
VPMADDWD ymm {k}{z}, ymm, ymm VPMADDWD_YMMi32_MASKmskw_YMMi16_YMMi16_AVX512EVEX.256.66.0F.WIG F5 /rAVX10.1 or AVX512BW + AVX512VL
VPMADDWD ymm {k}{z}, ymm, m256 VPMADDWD_YMMi32_MASKmskw_YMMi16_MEMi16_AVX512EVEX.256.66.0F.WIG F5 /rAVX10.1 or AVX512BW + AVX512VL
VPMADDWD zmm {k}{z}, zmm, zmm VPMADDWD_ZMMi32_MASKmskw_ZMMi16_ZMMi16_AVX512EVEX.512.66.0F.WIG F5 /rAVX10.1 or AVX512BW
VPMADDWD zmm {k}{z}, zmm, m512 VPMADDWD_ZMMi32_MASKmskw_ZMMi16_MEMi16_AVX512EVEX.512.66.0F.WIG F5 /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, xmm, m128
xmm {k}{z}, xmm, m128
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
ymm, ymm, m256
ymm {k}{z}, ymm, m256
ymm, ymm, ymmzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512
Sandy Bridge11 / 1p05 / 1p0
Haswell11 / 1p05 / 1p012 / 1p05 / 1p0
Broadwell10 / 1p05 / 1p011 / 1p05 / 1p0
Skylake11 / 0.5p015 / 0.5p0112 / 0.5p015 / 0.5p01
Skylake-SP, Ice Lake11 / 0.5p015 / 0.5p0112 / 0.5p015 / 0.5p015 / 0.5p0512 / 0.5p05
Alder Lake13 / 0.5p015 / 0.5p0113 / 0.5p015 / 0.5p01
Sapphire Rapids13 / 0.5p015 / 0.5p0113 / 0.5p015 / 0.5p015 / 1p013 / 1p0
Lunar Lake10 / 2V0 V14 / 2V0 V111 / 2.33V0 V14 / 2V0 V1
Piledriver9 / 1.5FPMMA FPU04 / 1FPMMA FPU0
Zen11 / 1FPU04 / 1FPU011 / 2FPU04 / 2FPU0
Zen 211 / 1FPU04 / 1FPU011 / 1FPU04 / 1FPU0
Zen 310 / 0.5FP0 FP33 / 0.5FP0 FP310 / 0.5FP0 FP33 / 0.5FP0 FP3
Zen 410 / 0.5FP0 FP33 / 0.5FP0 FP310 / 0.5FP0 FP33 / 0.5FP0 FP33 / 1FP0 FP310 / 1FP0 FP3
Jaguar7 / 1FPU0 VIMUL2 / 1FPU0 VIMUL

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.

Groups of 2 adjacent words are combined into one doubleword.
VPMADDWD: groups of 2 elementsResult doubleword i comes from words 2i to 2i+1 of xmm2 and xmm3. Result doublewords 3 to 0: sum, unchanged (bit 2 of k1 is 0), sum, sum.01234567xmm2a1110k1sumsumsumxmm101234567xmm3or m128b

The ymm and zmm forms repeat this in each 128-bit lane. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result doubleword i comes from words 2i to 2i+1 of xmm2 and xmm3. Result doublewords 3 to 0: sum, unchanged (bit 2 of k1 is 0), sum, sum.

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):
    x = 0
    for j in range(2 * i, 2 * i + 2):
        x += zmm2.sw[j] * src3.sw[j]
    if k1[i]:  # 1 without a write mask
        zmm1.d[i] = x
    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): 10 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
VPMADDWD xmm, xmm, xmm/m128 VPMADDWD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VPMADDWD xmm {k}{z}, xmm, xmm/m128 VPMADDWD ymm {k}{z}, ymm, ymm/m256 VPMADDWD zmm {k}{z}, zmm, zmm/m512
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
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.

VEX forms
avx-type-4
EVEX forms
AVX512-E4NF

Attributes

What else XED records about the forms. How to read.

EVEX forms
write masking

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPMADDWD, 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_madd_epi16 __m128i _mm_madd_epi16(__m128i __a, __m128i __b)

VPMADDWD xmm, xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_madd_epi16 __m128i _mm_mask_madd_epi16(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B)

VPMADDWD xmm {k}, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm_maskz_madd_epi16 __m128i _mm_maskz_madd_epi16(__mmask8 __U, __m128i __A, __m128i __B)

VPMADDWD xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl -mavx512bw

_mm256_madd_epi16 __m256i _mm256_madd_epi16(__m256i __a, __m256i __b)

VPMADDWD ymm, ymm, ymm VEX.256 -mavx2

_mm256_mask_madd_epi16 __m256i _mm256_mask_madd_epi16(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B)

VPMADDWD ymm {k}, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm256_maskz_madd_epi16 __m256i _mm256_maskz_madd_epi16(__mmask8 __U, __m256i __A, __m256i __B)

VPMADDWD ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl -mavx512bw

_mm512_madd_epi16 __m512i _mm512_madd_epi16(__m512i __A, __m512i __B)

VPMADDWD zmm, zmm, zmm EVEX.512 -mavx512bw

_mm512_mask_madd_epi16 __m512i _mm512_mask_madd_epi16(__m512i __W, __mmask16 __U, __m512i __A, __m512i __B)

VPMADDWD zmm {k}, zmm, zmm EVEX.512 -mavx512bw

_mm512_maskz_madd_epi16 __m512i _mm512_maskz_madd_epi16(__mmask16 __U, __m512i __A, __m512i __B)

VPMADDWD zmm {k}{z}, zmm, zmm EVEX.512 -mavx512bw

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
AVX

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX2

AVX2
CPUID.(EAX=07H,ECX=0):EBX[5] AVX2

Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
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 AVX instructions

All 253 AVX instructions

More AVX2 instructions

All 138 AVX2 instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-313 (PMADDWD)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. 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.