Instruction
VPDPBSSDS
Multiplies signed bytes by signed bytes, sums each group of four products and adds the sum to the matching 32-bit accumulator with signed saturation.
- Extensions
- Forms
- 10 (4 VEX, 6 EVEX)
- Data
- Intel XED v2026.08.23
VPDPBSSDS computes what VPDPBSSD does, four products of the signed bytes of its second and third operands added to each doubleword of the destination, but clamps the final sum to the signed 32-bit range, 80000000h to 7FFFFFFFh, instead of letting it wrap. VPDPBSSD’s page has the table of the six instructions that AVX-VNNI-INT8 added and their prefixes; the saturating forms take opcode 51h where the wrapping ones take 50h, and VPDPBSSDS shares F2 with VPDPBSSD. Each product lies between -16,256 and 16,384, so the four of them sum to between -65,024 and 65,536 and only the addition to the accumulator can saturate. VPDPBUSDS, the AVX512_VNNI instruction, explains when saturation helps.
Two encodings
- VEX (AVX-VNNI-INT8): XMM and YMM registers.
- EVEX (AVX10.2, or AVX10.1 with the AVX10_V1_AUX bit): ZMM as well, with masking and a broadcast doubleword.
Zen 5 has neither: its ten recorded cases, four VEX and six EVEX, all raised #UD.
In compiled code
C has no saturating addition, so neither GCC 14 nor Clang 23 derives
VPDPBSSDS from a loop: only the intrinsic gives it.
_mm256_dpbssds_epi32(acc, a, b), with -mavxvnniint8, is one
vpdpbssds ymm0, ymm1, ymm2 in both; the 512-bit intrinsics need
-mavx10.2, which Clang 23 accepts and GCC 14 does not.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPDPBSSDS xmm, xmm, xmm
VPDPBSSDS_XMMi32_XMM4i8_XMM4i8 | VEX.128.F2.0F38.W0 51 /r | AVX_VNNI_INT8 |
VPDPBSSDS xmm, xmm, m128
VPDPBSSDS_XMMi32_XMM4i8_MEM4i8 | VEX.128.F2.0F38.W0 51 /r | AVX_VNNI_INT8 |
VPDPBSSDS ymm, ymm, ymm
VPDPBSSDS_YMMi32_YMM4i8_YMM4i8 | VEX.256.F2.0F38.W0 51 /r | AVX_VNNI_INT8 |
VPDPBSSDS ymm, ymm, m256
VPDPBSSDS_YMMi32_YMM4i8_MEM4i8 | VEX.256.F2.0F38.W0 51 /r | AVX_VNNI_INT8 |
VPDPBSSDS xmm {k}{z}, xmm, xmm
VPDPBSSDS_XMMi32_MASKmskw_XMM4i8_XMM4i8_AVX512 | EVEX.128.F2.0F38.W0 51 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBSSDS xmm {k}{z}, xmm, m128/m32bcst
VPDPBSSDS_XMMi32_MASKmskw_XMM4i8_MEM4i8_AVX512 | EVEX.128.F2.0F38.W0 51 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBSSDS ymm {k}{z}, ymm, ymm
VPDPBSSDS_YMMi32_MASKmskw_YMM4i8_YMM4i8_AVX512 | EVEX.256.F2.0F38.W0 51 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBSSDS ymm {k}{z}, ymm, m256/m32bcst
VPDPBSSDS_YMMi32_MASKmskw_YMM4i8_MEM4i8_AVX512 | EVEX.256.F2.0F38.W0 51 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBSSDS zmm {k}{z}, zmm, zmm
VPDPBSSDS_ZMMi32_MASKmskw_ZMM4i8_ZMM4i8_AVX512 | EVEX.512.F2.0F38.W0 51 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBSSDS zmm {k}{z}, zmm, m512/m32bcst
VPDPBSSDS_ZMMi32_MASKmskw_ZMM4i8_MEM4i8_AVX512 | EVEX.512.F2.0F38.W0 51 /r | AVX10.2 or AVX10_V1_AUX |
Latency and throughput
| Model | xmm, xmm, xmmymm, ymm, ymm | xmm, xmm, m128 | ymm, ymm, m256 |
|---|---|---|---|
| Lunar Lake | 4 / 2V0 V1 | 10 / 2V0 V1 | 11 / 2.33V0 V1 |
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 bytes 4i to 4i+3 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.
if not cpuid_leaf(7, 1)[3] >> 4 & 1:
fault(UD) # CPUID: no AVX-VNNI-INT8
for i in range(VL // 32):
x = 0
for j in range(4 * i, 4 * i + 4):
x += ymm2.sb[j] * src3.sb[j]
ymm1.d[i] = ssat(ymm1.sd[i] + x, 32)
# ymm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 4 cases. Its cases ran where CPUID reported no AVX-VNNI-INT8, and every one raised an exception.
if not cpuid_leaf(7, 1)[3] >> 19 & 1:
fault(UD) # CPUID: no AVX10
ver = cpuid_leaf(0x24, 0)[1] & 0xFF
aux = cpuid_leaf(0x24, 1)[2] >> 2 & 1
if ver < 2 and not aux:
fault(UD) # neither AVX10.2 nor AVX10_V1_AUX
for i in range(VL // 32):
x = 0
for j in range(4 * i, 4 * i + 4):
x += zmm2.sb[j] * src3.sb[j]
if k1[i]:
zmm1.d[i] = ssat(zmm1.sd[i] + x, 32)
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): 6 cases. Its cases ran where CPUID reported no AVX10.2, and every one raised an exception.
Operands
| Operand | Kind | Action |
|---|---|---|
VPDPBSSDS xmm, xmm, xmm/m128 VPDPBSSDS ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | read, write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VPDPBSSDS xmm {k}{z}, xmm, xmm/m128/m32bcst VPDPBSSDS ymm {k}{z}, ymm, ymm/m256/m32bcst VPDPBSSDS 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 VPDPBSSDS, 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_dpbssds_epi32
__m128i _mm_dpbssds_epi32(__m128i __W, __m128i __A, __m128i __B) |
|
_mm_mask_dpbssds_epi32
__m128i _mm_mask_dpbssds_epi32(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_dpbssds_epi32
__m128i _mm_maskz_dpbssds_epi32(__mmask8 __U, __m128i __W, __m128i __A, __m128i __B) |
|
_mm256_dpbssds_epi32
__m256i _mm256_dpbssds_epi32(__m256i __W, __m256i __A, __m256i __B) |
|
_mm256_mask_dpbssds_epi32
__m256i _mm256_mask_dpbssds_epi32(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_dpbssds_epi32
__m256i _mm256_maskz_dpbssds_epi32(__mmask8 __U, __m256i __W, __m256i __A, __m256i __B) |
|
_mm512_dpbssds_epi32
__m512i _mm512_dpbssds_epi32(__m512i __W, __m512i __A, __m512i __B) |
|
_mm512_mask_dpbssds_epi32
__m512i _mm512_mask_dpbssds_epi32(__m512i __W, __mmask16 __U, __m512i __A, __m512i __B) |
|
_mm512_maskz_dpbssds_epi32
__m512i _mm512_maskz_dpbssds_epi32(__mmask16 __U, __m512i __W, __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_INT8 | AVX_VNNI_INT8 | Arrow Lake, Panther Lake, Nova Lake, Diamond Rapids, Sierra Forest, Clearwater Forest, Zen 6 |
AVX512_VNNI_INT8_128 | AVX10.2 or AVX10_V1_AUX | Nova Lake, Diamond Rapids |
AVX512_VNNI_INT8_256 | Same as AVX512_VNNI_INT8_128 | Same as AVX512_VNNI_INT8_128 |
AVX512_VNNI_INT8_512 | Same as AVX512_VNNI_INT8_128 | Same as AVX512_VNNI_INT8_128 |
More AVX-VNNI-INT8 instructions
More AVX10.2 instructions
- VFNMSUB132BF16
- VFNMSUB213BF16
- VFNMSUB231BF16
- VFPCLASSBF16
- VGETEXPBF16
- VGETMANTBF16
- VMAXBF16
- VMINBF16
- VMINMAXBF16
- VMINMAXPD
- VMINMAXPH
- VMINMAXPS
- VMINMAXSD
- VMINMAXSH
- VMINMAXSS
- VMOVD
- VMOVW
- VMPSADBW
- VMULBF16
- VPDPBSSD
- VPDPBSUD
- VPDPBSUDS
- VPDPBUUD
- VPDPBUUDS
- VPDPWSUD
- VPDPWSUDS
- VPDPWUSD
- VPDPWUSDS
- VPDPWUUD
- VPDPWUUDS
- VRCPBF16
- VREDUCEBF16
- VRNDSCALEBF16
- VRSQRTBF16
- VSCALEFBF16
- VSQRTBF16
- VSUBBF16
- VUCOMXSD
- VUCOMXSH
- VUCOMXSS
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-478 (VPDPB[SU,UU,SS]D[,S])
- Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
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.