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

VPDPBSSD is the dot-product step for bytes that are both signed. In each doubleword it multiplies the four signed bytes of the second operand by the four signed bytes of the third, adds the four products to the destination’s doubleword, and lets the sum wrap. VPDPBUSD, whose page explains the idea, takes one unsigned and one signed operand. AVX-VNNI-INT8 added the other combinations, each with a saturating twin:

Instruction2nd operand3rd operandSaturating
VPDPBSSDsignedsignedVPDPBSSDS
VPDPBSUDsignedunsignedVPDPBSUDS
VPDPBUUDunsignedunsignedVPDPBUUDS

VPDPBSUD is VPDPBUSD with its sources swapped. All of them share opcode 50h (51h for the saturating ones) and differ in the prefix: 66 for VPDPBUSD, F2 for VPDPBSSD, F3 for VPDPBSUD and none for VPDPBUUD.

A product of two signed bytes lies between -16256 (-128 times 127) and 16384 (-128 times -128), so a group of four sums to at most 65536 in magnitude: only the addition to the accumulator can overflow.

Two encodings

  • VEX (AVX-VNNI-INT8): xmm and ymm. Intel’s optimization manual lists it among the new instructions of the Crestmont E-core (Section 4.1.8.3).
  • EVEX (AVX10.2): zmm as well, with masking and embedded broadcast.

Zen 5 has neither: its ten recorded cases, four VEX and six EVEX, all raised #UD.

In compiled code

GCC 14 at -O2 with -march=arrowlake turns s += a[i] * b[i] over int8_t arrays into VPDPBSSD on ymm registers with a memory operand (and the same loop with uint8_t for a into VPDPBUSD), through pointer parameters as well when the count is a constant; a pointer loop of unknown length stays scalar at -O2 and becomes VPDPBSSD at -O3. Clang 23 does not use it even at -O3: it widens both arrays to words with VPMOVSXBW and multiplies pairs with VPMADDWD, the route it also takes for -march=znver5, which lacks VNNI-INT8. The intrinsic _mm256_dpbssd_epi32(acc, a, b) needs -mavxvnniint8; the 512-bit and masked ones need -mavx10.2.

In the optimization guide

What the optimization guide says about VPDPBSSD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Crestmont and Gracemont

  • Vectors and AVX2: Crestmont runs the VNNI dot products at twice Gracemont’s rate.

Forms

Every encoding of VPDPBSSD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPDPBSSD xmm, xmm, xmm VPDPBSSD_XMMi32_XMM4i8_XMM4i8VEX.128.F2.0F38.W0 50 /rAVX_VNNI_INT8
VPDPBSSD xmm, xmm, m128 VPDPBSSD_XMMi32_XMM4i8_MEM4i8VEX.128.F2.0F38.W0 50 /rAVX_VNNI_INT8
VPDPBSSD ymm, ymm, ymm VPDPBSSD_YMMi32_YMM4i8_YMM4i8VEX.256.F2.0F38.W0 50 /rAVX_VNNI_INT8
VPDPBSSD ymm, ymm, m256 VPDPBSSD_YMMi32_YMM4i8_MEM4i8VEX.256.F2.0F38.W0 50 /rAVX_VNNI_INT8
VPDPBSSD xmm {k}{z}, xmm, xmm VPDPBSSD_XMMi32_MASKmskw_XMM4i8_XMM4i8_AVX512EVEX.128.F2.0F38.W0 50 /rAVX10.2 or AVX10_V1_AUX
VPDPBSSD xmm {k}{z}, xmm, m128/m32bcst VPDPBSSD_XMMi32_MASKmskw_XMM4i8_MEM4i8_AVX512EVEX.128.F2.0F38.W0 50 /rAVX10.2 or AVX10_V1_AUX
VPDPBSSD ymm {k}{z}, ymm, ymm VPDPBSSD_YMMi32_MASKmskw_YMM4i8_YMM4i8_AVX512EVEX.256.F2.0F38.W0 50 /rAVX10.2 or AVX10_V1_AUX
VPDPBSSD ymm {k}{z}, ymm, m256/m32bcst VPDPBSSD_YMMi32_MASKmskw_YMM4i8_MEM4i8_AVX512EVEX.256.F2.0F38.W0 50 /rAVX10.2 or AVX10_V1_AUX
VPDPBSSD zmm {k}{z}, zmm, zmm VPDPBSSD_ZMMi32_MASKmskw_ZMM4i8_ZMM4i8_AVX512EVEX.512.F2.0F38.W0 50 /rAVX10.2 or AVX10_V1_AUX
VPDPBSSD zmm {k}{z}, zmm, m512/m32bcst VPDPBSSD_ZMMi32_MASKmskw_ZMM4i8_MEM4i8_AVX512EVEX.512.F2.0F38.W0 50 /rAVX10.2 or AVX10_V1_AUX

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, xmm
ymm, ymm, ymm
xmm, xmm, m128ymm, ymm, m256
Lunar Lake4 / 2V0 V110 / 2V0 V111 / 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.

Groups of 4 adjacent bytes are combined into one doubleword and added to the destination's old value.
VPDPBSSD: groups of 4 elementsResult 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), +=, +=.0123456789101112131415xmm2a1110k1+=+=+=xmm10123456789101112131415xmm3or 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}. 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.

VEX forms
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] = ymm1.d[i] + x
# ymm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 4 cases. Its cases ran where CPUID reported no AVX-VNNI-INT8, and every one raised an exception.

EVEX forms
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] = 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 up

Run on AMD Zen 5 (EPYC 9645): 6 cases. Its cases ran where CPUID reported no AVX10.2, and every one raised an exception.

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
VPDPBSSD xmm, xmm, xmm/m128 VPDPBSSD ymm, ymm, ymm/m256
xmm, ymmexplicitread, write
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VPDPBSSD xmm {k}{z}, xmm, xmm/m128/m32bcst VPDPBSSD ymm {k}{z}, ymm, ymm/m256/m32bcst VPDPBSSD zmm {k}{z}, zmm, zmm/m512/m32bcst
xmm, ymm, zmmexplicitread, write (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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 VPDPBSSD, 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_dpbssd_epi32 __m128i _mm_dpbssd_epi32(__m128i __W, __m128i __A, __m128i __B)

VPDPBSSD xmm, xmm, xmm VEX.128 -mavxvnniint8

VPDPBSSD xmm, xmm, xmm VEX.128 -mavx -mavxvnniint8with AVX enabled

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

VPDPBSSD xmm {k}, xmm, xmm EVEX.128 -mavx10.2

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

VPDPBSSD xmm {k}{z}, xmm, xmm EVEX.128 -mavx10.2

_mm256_dpbssd_epi32 __m256i _mm256_dpbssd_epi32(__m256i __W, __m256i __A, __m256i __B)

VPDPBSSD ymm, ymm, ymm VEX.256 -mavxvnniint8

VPDPBSSD ymm, ymm, ymm VEX.256 -mavx -mavxvnniint8with AVX enabled

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

VPDPBSSD ymm {k}, ymm, ymm EVEX.256 -mavx10.2

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

VPDPBSSD ymm {k}{z}, ymm, ymm EVEX.256 -mavx10.2

_mm512_dpbssd_epi32 __m512i _mm512_dpbssd_epi32(__m512i __W, __m512i __A, __m512i __B)

VPDPBSSD zmm, zmm, zmm EVEX.512 -mavx10.2

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

VPDPBSSD zmm {k}, zmm, zmm EVEX.512 -mavx10.2

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

VPDPBSSD zmm {k}{z}, zmm, zmm EVEX.512 -mavx10.2

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_VNNI_INT8

AVX_VNNI_INT8
CPUID.(EAX=07H,ECX=1):EDX[4] AVX_VNNI_INT8

Arrow Lake, Panther Lake, Nova Lake, Diamond Rapids, Sierra Forest, Clearwater Forest, Zen 6
AVX512_VNNI_INT8_128

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

or

AVX10_V1_AUX
CPUID.(EAX=24H,ECX=1):ECX[2] AVX10_V1_AUX

Nova Lake, Diamond Rapids
AVX512_VNNI_INT8_256
Same as AVX512_VNNI_INT8_128Same as AVX512_VNNI_INT8_128
AVX512_VNNI_INT8_512
Same as AVX512_VNNI_INT8_128Same as AVX512_VNNI_INT8_128

More AVX-VNNI-INT8 instructions

More AVX10.2 instructions

All 96 AVX10.2 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 2C, page 5-478 (VPDPB[SU,UU,SS]D[,S])
  6. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 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.