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

VPDPWUUD multiplies, in each doubleword, the two unsigned words of its second operand by the two unsigned words of its third, adds both products to the destination’s doubleword and lets the sum wrap modulo 2^32. VPDPWSUD’s page has the table of the AVX-VNNI-INT16 instructions; this one is opcode D2h in map 0F38 with no prefix, and VPDPWUUDS is its saturating twin. Before it, VPMADDWD and VPDPWSSD read every word as signed, so a word above 7FFFh counted as negative.

Products near 2^32

A product of two unsigned words is at most FFFE0001h (65,535 squared), just under 2^32, so two products alone can pass it: two such products sum to 1FFFC0002h and leave FFFC0002h. A dot product that must not wrap needs either VPDPWUUDS or inputs that keep the sum in range.

Two encodings

  • VEX (AVX-VNNI-INT16): xmm and ymm.
  • 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

At -O2 with -march=arrowlake-s, GCC 14 turns s += (unsigned)a[i] * b[i] over two uint16_t arrays of 1,024 elements, with an unsigned sum, into VPDPWUUD on ymm registers with one array as the memory operand; the cast matters, since two uint16_t promoted to int can overflow it. Clang 23 widens both arrays with VPMOVZXWD and multiplies with VPMULLD. The intrinsic is _mm256_dpwuud_avx_epi32 in GCC 14 and _mm256_dpwuud_epi32 in Clang 23 and Intel’s manual.

Forms

Every encoding of VPDPWUUD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPDPWUUD xmm, xmm, xmm VPDPWUUD_XMMu32_XMM2u16_XMM2u16VEX.128.NP.0F38.W0 D2 /rAVX_VNNI_INT16
VPDPWUUD xmm, xmm, m128 VPDPWUUD_XMMu32_XMM2u16_MEM2u16VEX.128.NP.0F38.W0 D2 /rAVX_VNNI_INT16
VPDPWUUD ymm, ymm, ymm VPDPWUUD_YMMu32_YMM2u16_YMM2u16VEX.256.NP.0F38.W0 D2 /rAVX_VNNI_INT16
VPDPWUUD ymm, ymm, m256 VPDPWUUD_YMMu32_YMM2u16_MEM2u16VEX.256.NP.0F38.W0 D2 /rAVX_VNNI_INT16
VPDPWUUD xmm {k}{z}, xmm, xmm VPDPWUUD_XMMu32_MASKmskw_XMM2u16_XMM2u16_AVX512EVEX.128.NP.0F38.W0 D2 /rAVX10.2 or AVX10_V1_AUX
VPDPWUUD xmm {k}{z}, xmm, m128/m32bcst VPDPWUUD_XMMu32_MASKmskw_XMM2u16_MEM2u16_AVX512EVEX.128.NP.0F38.W0 D2 /rAVX10.2 or AVX10_V1_AUX
VPDPWUUD ymm {k}{z}, ymm, ymm VPDPWUUD_YMMu32_MASKmskw_YMM2u16_YMM2u16_AVX512EVEX.256.NP.0F38.W0 D2 /rAVX10.2 or AVX10_V1_AUX
VPDPWUUD ymm {k}{z}, ymm, m256/m32bcst VPDPWUUD_YMMu32_MASKmskw_YMM2u16_MEM2u16_AVX512EVEX.256.NP.0F38.W0 D2 /rAVX10.2 or AVX10_V1_AUX
VPDPWUUD zmm {k}{z}, zmm, zmm VPDPWUUD_ZMMu32_MASKmskw_ZMM2u16_ZMM2u16_AVX512EVEX.512.NP.0F38.W0 D2 /rAVX10.2 or AVX10_V1_AUX
VPDPWUUD zmm {k}{z}, zmm, m512/m32bcst VPDPWUUD_ZMMu32_MASKmskw_ZMM2u16_MEM2u16_AVX512EVEX.512.NP.0F38.W0 D2 /rAVX10.2 or AVX10_V1_AUX

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 and added to the destination's old value.
VPDPWUUD: groups of 2 elementsResult 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), +=, +=.01234567xmm2a1110k1+=+=+=xmm101234567xmm3or 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 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.

VEX forms
if not cpuid_leaf(7, 1)[3] >> 10 & 1:
    fault(UD)  # CPUID: no AVX-VNNI-INT16
for i in range(VL // 32):
    x = 0
    for j in range(2 * i, 2 * i + 2):
        x += ymm2.w[j] * src3.w[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-INT16, 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(2 * i, 2 * i + 2):
        x += zmm2.w[j] * src3.w[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
VPDPWUUD xmm, xmm, xmm/m128 VPDPWUUD ymm, ymm, ymm/m256
xmm, ymmexplicitread, write
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VPDPWUUD xmm {k}{z}, xmm, xmm/m128/m32bcst VPDPWUUD ymm {k}{z}, ymm, ymm/m256/m32bcst VPDPWUUD 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 VPDPWUUD, 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_dpwuud_epi32 __m128i _mm_dpwuud_epi32(__m128i __W, __m128i __A, __m128i __B)

VPDPWUUD xmm, xmm, xmm VEX.128 -mavxvnniint16

VPDPWUUD xmm, xmm, xmm VEX.128 -mavx -mavxvnniint16with AVX enabled

_mm_mask_dpwuud_epi32 __m128i _mm_mask_dpwuud_epi32(__m128i __A, __mmask8 __U, __m128i __B, __m128i __C)

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

_mm_maskz_dpwuud_epi32 __m128i _mm_maskz_dpwuud_epi32(__mmask8 __U, __m128i __A, __m128i __B, __m128i __C)

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

_mm256_dpwuud_epi32 __m256i _mm256_dpwuud_epi32(__m256i __W, __m256i __A, __m256i __B)

VPDPWUUD ymm, ymm, ymm VEX.256 -mavxvnniint16

VPDPWUUD ymm, ymm, ymm VEX.256 -mavx -mavxvnniint16with AVX enabled

_mm256_mask_dpwuud_epi32 __m256i _mm256_mask_dpwuud_epi32(__m256i __A, __mmask8 __U, __m256i __B, __m256i __C)

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

_mm256_maskz_dpwuud_epi32 __m256i _mm256_maskz_dpwuud_epi32(__mmask8 __U, __m256i __A, __m256i __B, __m256i __C)

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

_mm512_dpwuud_epi32 __m512i _mm512_dpwuud_epi32(__m512i __A, __m512i __B, __m512i __C)

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

_mm512_mask_dpwuud_epi32 __m512i _mm512_mask_dpwuud_epi32(__m512i __A, __mmask16 __U, __m512i __B, __m512i __C)

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

_mm512_maskz_dpwuud_epi32 __m512i _mm512_maskz_dpwuud_epi32(__mmask16 __U, __m512i __A, __m512i __B, __m512i __C)

VPDPWUUD 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_INT16

AVX_VNNI_INT16
CPUID.(EAX=07H,ECX=1):EDX[10] AVX_VNNI_INT16

Arrow Lake, Panther Lake, Nova Lake, Diamond Rapids, Clearwater Forest

Note: Intel's extensions reference introduces these instructions with Arrow Lake S, and GCC's -march=arrowlake, which it selects for Arrow Lake H and U, leaves them out.

AVX512_VNNI_INT16_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_INT16_256
Same as AVX512_VNNI_INT16_128Same as AVX512_VNNI_INT16_128
AVX512_VNNI_INT16_512
Same as AVX512_VNNI_INT16_128Same as AVX512_VNNI_INT16_128

More AVX-VNNI-INT16 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. 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.
  3. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-491 (VPDPW[SU,US,UU]D[,S])
  4. 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, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.