Instruction
VPDPWSSD
Multiplies pairs of signed words, adds both products to the matching 32-bit accumulator.
VPDPWSSD is the word member of the VNNI dot products. In each 32-bit element it multiplies the two signed words of the first source by the two signed words at the same positions of the second, and adds both products to the doubleword already in the destination. That is VPMADDWD followed by VPADDD in one instruction, with the same result bit for bit: both wrap modulo 2^32, including PMADDWD’s single overflow when all four words are -32,768. Its byte sibling VPDPBUSD differs more from the sequence it replaces, which saturates at 16 bits.
Wrapping or saturating
The addition into the accumulator wraps without a flag. In a case recorded on Zen 5 with the VEX form, an accumulator of 7FFFFFFFh plus the products 1 times 0 and 1 times 1 gave 80000000h. VPDPWSSDS clamps the sum to the signed 32-bit range instead. The other word variants of AVX-VNNI-INT16, VPDPWSUD, VPDPWUSD and their kin, read one or both sources as unsigned.
Two encodings
The EVEX forms belong to AVX512_VNNI, now part of AVX10.1, with masking,
broadcast of a doubleword and 512-bit vectors. AVX-VNNI has VEX forms
for xmm and ymm only, whose intrinsics are named apart, for example
_mm256_dpwssd_avx_epi32. Zen 5 has both: every VEX case recorded here
ran. With both available, Clang 23 picks the shorter VEX encoding for
ymm registers and prints it as {vex} vpdpwssd.
Where it appears
Intel’s optimization manual suggests VPDPWSSD for inference where 8-bit data with VPDPBUSD costs too much accuracy, and expects no gain from it on client processors such as Ice Lake (Section 8.2.2).
Compilers use it for 16-bit dot products. For s += a[i] * b[i] over
1,024 int16_t pairs, GCC 14 at -O2 with -march=znver5 or
-mavx512vnni emits VPDPWSSD on zmm registers, while Clang 23 keeps
VPMADDWD and VPADDD. Clang uses it elsewhere: for a dot product of
uint8_t and int8_t arrays it widens the bytes to words and
accumulates with VPDPWSSD, where GCC emits VPDPBUSD, and for a rounded
Q15 product it puts the rounding constant 4000h in the accumulator (see
VPMULHRSW).
AMD’s Zen 5 guide lists VPDPWSSD as one macro-op with a latency of 4 cycles, as for VPDPBUSD.
In the optimization guide
What the optimization guide says about VPDPWSSD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Ice Lake to Rocket Lake
- Vectors and AVX-512: VPDPBUSD, which replaces a three-instruction sequence of byte multiplications and additions, gains only two times on the client parts against three times on the servers, because on the clients the older sequence’s addition can also use port 5.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPDPWSSD xmm, xmm, xmm
VPDPWSSD_XMMi32_XMMu32_XMMu32 | VEX.128.66.0F38.W0 52 /r | AVX_VNNI |
VPDPWSSD xmm, xmm, m128
VPDPWSSD_XMMi32_XMMu32_MEMu32 | VEX.128.66.0F38.W0 52 /r | AVX_VNNI |
VPDPWSSD ymm, ymm, ymm
VPDPWSSD_YMMi32_YMMu32_YMMu32 | VEX.256.66.0F38.W0 52 /r | AVX_VNNI |
VPDPWSSD ymm, ymm, m256
VPDPWSSD_YMMi32_YMMu32_MEMu32 | VEX.256.66.0F38.W0 52 /r | AVX_VNNI |
VPDPWSSD xmm {k}{z}, xmm, xmm
VPDPWSSD_XMMi32_MASKmskw_XMMi16_XMMu32_AVX512 | EVEX.128.66.0F38.W0 52 /r | AVX10.1 or AVX512_VNNI + AVX512VL |
VPDPWSSD xmm {k}{z}, xmm, m128/m32bcst
VPDPWSSD_XMMi32_MASKmskw_XMMi16_MEMu32_AVX512 | EVEX.128.66.0F38.W0 52 /r | AVX10.1 or AVX512_VNNI + AVX512VL |
VPDPWSSD ymm {k}{z}, ymm, ymm
VPDPWSSD_YMMi32_MASKmskw_YMMi16_YMMu32_AVX512 | EVEX.256.66.0F38.W0 52 /r | AVX10.1 or AVX512_VNNI + AVX512VL |
VPDPWSSD ymm {k}{z}, ymm, m256/m32bcst
VPDPWSSD_YMMi32_MASKmskw_YMMi16_MEMu32_AVX512 | EVEX.256.66.0F38.W0 52 /r | AVX10.1 or AVX512_VNNI + AVX512VL |
VPDPWSSD zmm {k}{z}, zmm, zmm
VPDPWSSD_ZMMi32_MASKmskw_ZMMi16_ZMMu32_AVX512 | EVEX.512.66.0F38.W0 52 /r | AVX10.1 or AVX512_VNNI |
VPDPWSSD zmm {k}{z}, zmm, m512/m32bcst
VPDPWSSD_ZMMi32_MASKmskw_ZMMi16_MEMu32_AVX512 | EVEX.512.66.0F38.W0 52 /r | AVX10.1 or AVX512_VNNI |
Latency and throughput
| Model | xmm, xmm, xmmymm, ymm, ymm | xmm, xmm, m128 | ymm, ymm, m256 | xmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | xmm {k}{z}, xmm, m128/m32bcst | ymm {k}{z}, ymm, m256/m32bcst | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m32bcst |
|---|---|---|---|---|---|---|---|---|
| Skylake-SP, Ice Lake | 5 / 0.5p01 | 11 / 0.5p01 | 12 / 0.5p01 | 5 / 0.5p05 | 12 / 0.5p05 | |||
| Alder Lake | 5 / 0.5p01 | 13 / 0.5p01 | 13 / 0.5p01 | |||||
| Sapphire Rapids | 5 / 0.5p01 | 13 / 0.5p01 | 13 / 0.5p01 | 5 / 0.5p01 | 13 / 0.5p01 | 13 / 0.5p01 | 5 / 1p0 | 13 / 1p0 |
| Lunar Lake | 4 / 2V0 V1 | 10 / 2V0 V1 | 11 / 2.33V0 V1 | |||||
| Zen 4 | 4 / 21FP0 FP1 | 10 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 4 / 2FP0 FP1 | 10 / 1FP0 FP3 | |||
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.
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}. With m32bcst, one doubleword from memory stands for every element of the last source.
Result doubleword i comes from words 2i to 2i+1 of xmm2 and xmm3. Result doublewords 3 to 0: +=, unchanged (bit 2 of k1 is 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 // 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] = zmm1.d[i] + x
elif zeroing:
zmm1.d[i] = 0
# else: zmm1.d[i] keeps its value
# m32bcst: src3.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 10 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPDPWSSD xmm, xmm, xmm/m128 VPDPWSSD ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | read, write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VPDPWSSD xmm {k}{z}, xmm, xmm/m128/m32bcst VPDPWSSD ymm {k}{z}, ymm, ymm/m256/m32bcst VPDPWSSD zmm {k}{z}, zmm, zmm/m512/m32bcst | ||
xmm, ymm, zmm | explicit | read, write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | explicit | read |
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-E4
Attributes
What else XED records about the forms. How to read.
- EVEX forms
- write masking
- EVEX memory forms
- embedded broadcast (tuple Full); memory fault suppression
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VPDPWSSD, 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.
| Intrinsic | Compiles to |
|---|---|
_mm_dpwssd_avx_epi32
__m128i _mm_dpwssd_avx_epi32(__m128i __S, __m128i __A, __m128i __B) |
|
_mm_dpwssd_epi32
__m128i _mm_dpwssd_epi32(__m128i S, __m128i A, __m128i B) |
|
_mm_mask_dpwssd_epi32
__m128i _mm_mask_dpwssd_epi32(__m128i __S, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_dpwssd_epi32
__m128i _mm_maskz_dpwssd_epi32(__mmask8 __U, __m128i __S, __m128i __A, __m128i __B) |
|
_mm256_dpwssd_avx_epi32
__m256i _mm256_dpwssd_avx_epi32(__m256i __S, __m256i __A, __m256i __B) |
|
_mm256_dpwssd_epi32
__m256i _mm256_dpwssd_epi32(__m256i S, __m256i A, __m256i B) |
|
_mm256_mask_dpwssd_epi32
__m256i _mm256_mask_dpwssd_epi32(__m256i __S, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_dpwssd_epi32
__m256i _mm256_maskz_dpwssd_epi32(__mmask8 __U, __m256i __S, __m256i __A, __m256i __B) |
|
_mm512_dpwssd_epi32
__m512i _mm512_dpwssd_epi32(__m512i __S, __m512i __A, __m512i __B) |
|
_mm512_mask_dpwssd_epi32
__m512i _mm512_mask_dpwssd_epi32(__m512i __S, __mmask16 __U, __m512i __A, __m512i __B) |
|
_mm512_maskz_dpwssd_epi32
__m512i _mm512_maskz_dpwssd_epi32(__mmask16 __U, __m512i __S, __m512i __A, __m512i __B) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX_VNNI | AVX_VNNI | Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Zen 5, Zen 6 |
AVX512_VNNI_128 | AVX10.1 or AVX512_VNNI + AVX512VL | Ice Lake (client), Tiger Lake, Nova Lake, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6 |
AVX512_VNNI_256 | Same as AVX512_VNNI_128 | Same as AVX512_VNNI_128 |
AVX512_VNNI_512 | AVX10.1 or AVX512_VNNI | Same as AVX512_VNNI_128 |
More AVX-VNNI instructions
More AVX10.1 instructions
- VPCMPEQQ
- VPCMPEQW
- VPCMPGTB
- VPCMPGTD
- VPCMPGTQ
- VPCMPGTW
- VPCMPQ
- VPCMPUB
- VPCMPUD
- VPCMPUQ
- VPCMPUW
- VPCMPW
- VPCOMPRESSB
- VPCOMPRESSD
- VPCOMPRESSQ
- VPCOMPRESSW
- VPCONFLICTD
- VPCONFLICTQ
- VPDPBUSD
- VPDPBUSDS
- VPDPWSSDS
- VPERMB
- VPERMD
- VPERMI2B
- VPERMI2D
- VPERMI2PD
- VPERMI2PS
- VPERMI2Q
- VPERMI2W
- VPERMILPD
- VPERMILPS
- VPERMPD
- VPERMPS
- VPERMQ
- VPERMT2B
- VPERMT2D
- VPERMT2PD
- VPERMT2PS
- VPERMT2Q
- VPERMT2W
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-487 (VPDPWSSD)
- Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
- 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.