Instruction
VPDPBUUD
Multiplies unsigned bytes by unsigned bytes, sums each group of four products and adds the sum to the matching 32-bit accumulator.
- Extensions
- Forms
- 10 (4 VEX, 6 EVEX)
- Data
- Intel XED v2026.08.23
VPDPBUUD is the dot-product step for two operands of unsigned bytes. In each doubleword it multiplies the four unsigned bytes of the second operand by the four unsigned bytes of the third, adds the four products to the destination’s doubleword, and lets the sum wrap modulo 2^32. VPDPBUSD explains the idea, and VPDPBSSD’s table shows the other sign combinations that AVX-VNNI-INT8 added; VPDPBUUD is the one with no prefix byte (opcode 50h), and VPDPBUUDS is its saturating twin, which clamps at FFFFFFFFh as an unsigned sum.
Before it, a dot product of two unsigned byte arrays could not use VPDPBUSD directly, since that instruction reads the bytes of its third operand as signed, and a value above 127 there would count as negative. A product of two unsigned bytes is at most 65,025 (255 times 255), and four of them at most 260,100, so again only the addition to the accumulator can overflow.
Two encodings
- VEX (AVX-VNNI-INT8): xmm and ymm, which Intel’s optimization manual lists among the Crestmont E-core’s additions (Section 4.1.8.3).
- EVEX (AVX10.2): 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 and left the destination as it was.
In compiled code
GCC 14 at -O2 with -march=arrowlake turns s += a[i] * b[i] over two
uint8_t arrays of 1,024 elements into VPDPBUUD on ymm registers, one
array read from memory. Clang 23 does not use it there: it widens both
arrays to words with VPMOVZXBW and multiplies pairs
with VPMADDWD. Both compile the intrinsic
_mm256_dpbuud_epi32(acc, a, b), which needs -mavxvnniint8, to one
VPDPBUUD.
In the optimization guide
What the optimization guide says about VPDPBUUD, 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
| Instruction | Encoding | Requires |
|---|---|---|
VPDPBUUD xmm, xmm, xmm
VPDPBUUD_XMMu32_XMM4u8_XMM4u8 | VEX.128.NP.0F38.W0 50 /r | AVX_VNNI_INT8 |
VPDPBUUD xmm, xmm, m128
VPDPBUUD_XMMu32_XMM4u8_MEM4u8 | VEX.128.NP.0F38.W0 50 /r | AVX_VNNI_INT8 |
VPDPBUUD ymm, ymm, ymm
VPDPBUUD_YMMu32_YMM4u8_YMM4u8 | VEX.256.NP.0F38.W0 50 /r | AVX_VNNI_INT8 |
VPDPBUUD ymm, ymm, m256
VPDPBUUD_YMMu32_YMM4u8_MEM4u8 | VEX.256.NP.0F38.W0 50 /r | AVX_VNNI_INT8 |
VPDPBUUD xmm {k}{z}, xmm, xmm
VPDPBUUD_XMMu32_MASKmskw_XMM4u8_XMM4u8_AVX512 | EVEX.128.NP.0F38.W0 50 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBUUD xmm {k}{z}, xmm, m128/m32bcst
VPDPBUUD_XMMu32_MASKmskw_XMM4u8_MEM4u8_AVX512 | EVEX.128.NP.0F38.W0 50 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBUUD ymm {k}{z}, ymm, ymm
VPDPBUUD_YMMu32_MASKmskw_YMM4u8_YMM4u8_AVX512 | EVEX.256.NP.0F38.W0 50 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBUUD ymm {k}{z}, ymm, m256/m32bcst
VPDPBUUD_YMMu32_MASKmskw_YMM4u8_MEM4u8_AVX512 | EVEX.256.NP.0F38.W0 50 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBUUD zmm {k}{z}, zmm, zmm
VPDPBUUD_ZMMu32_MASKmskw_ZMM4u8_ZMM4u8_AVX512 | EVEX.512.NP.0F38.W0 50 /r | AVX10.2 or AVX10_V1_AUX |
VPDPBUUD zmm {k}{z}, zmm, m512/m32bcst
VPDPBUUD_ZMMu32_MASKmskw_ZMM4u8_MEM4u8_AVX512 | EVEX.512.NP.0F38.W0 50 /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.b[j] * src3.b[j]
ymm1.d[i] = ymm1.d[i] + x
# 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.b[j] * src3.b[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 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 |
|---|---|---|
VPDPBUUD xmm, xmm, xmm/m128 VPDPBUUD ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | read, write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VPDPBUUD xmm {k}{z}, xmm, xmm/m128/m32bcst VPDPBUUD ymm {k}{z}, ymm, ymm/m256/m32bcst VPDPBUUD 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 VPDPBUUD, 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_dpbuud_epi32
__m128i _mm_dpbuud_epi32(__m128i __W, __m128i __A, __m128i __B) |
|
_mm_mask_dpbuud_epi32
__m128i _mm_mask_dpbuud_epi32(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_dpbuud_epi32
__m128i _mm_maskz_dpbuud_epi32(__mmask8 __U, __m128i __W, __m128i __A, __m128i __B) |
|
_mm256_dpbuud_epi32
__m256i _mm256_dpbuud_epi32(__m256i __W, __m256i __A, __m256i __B) |
|
_mm256_mask_dpbuud_epi32
__m256i _mm256_mask_dpbuud_epi32(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_dpbuud_epi32
__m256i _mm256_maskz_dpbuud_epi32(__mmask8 __U, __m256i __W, __m256i __A, __m256i __B) |
|
_mm512_dpbuud_epi32
__m512i _mm512_dpbuud_epi32(__m512i __W, __m512i __A, __m512i __B) |
|
_mm512_mask_dpbuud_epi32
__m512i _mm512_mask_dpbuud_epi32(__m512i __W, __mmask16 __U, __m512i __A, __m512i __B) |
|
_mm512_maskz_dpbuud_epi32
__m512i _mm512_maskz_dpbuud_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
- VPDPBSSDS
- VPDPBSUD
- VPDPBSUDS
- 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)
- 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.