Extensions
Forms
6 (6 EVEX)
Data
Intel XED v2026.08.23

VDPPHPS is the dot-product step for half precision: each doubleword of the two sources holds a pair of FP16 values, and the instruction adds both products of a pair to the single in the same position of the destination, 4, 8 or 16 sums for an xmm, ymm or zmm register. The third source can be a register, memory, or one pair broadcast from memory, and a write mask has one bit per single. It does for FP16 what VDPBF16PS does for bfloat16, in the slot beside it: opcode 52h in map 0F38, W0, with no prefix, where VDPBF16PS has F3 and VPDPWSSD, the integer word version, 66. Only AVX10.2 has it, not the narrower AVX10_V1_AUX bit that reports some of its conversions and integer dot products.

Two roundings, fixed rules

The products are added one pair at a time, the upper half of the doubleword first, each sum rounded to a single to nearest even. A product of two halves needs at most 22 significant bits and fits a single exactly, so the roundings are those of the sums: adding two products and the accumulator can give a different single from the exact sum rounded once.

MXCSR is neither read nor written, and nothing is flagged or raised. The rules are fixed instead: FP16 inputs are taken as they are, denormals too, while a denormal accumulator counts as zero and a denormal result becomes zero. VDPBF16PS treats its bfloat16 denormals as zeros; the FP16 ones here count. When several inputs are NaNs, AVX10.2’s description returns the first one, quieted, in the order lower pair, upper pair, accumulator.

In our builds

GCC 14 has no -mavx10.2. In Clang 23 with -mavx10.2, _mm512_dpph_ps(w, a, b) becomes vdpphps zmm0, zmm1, zmm2 with the accumulator w in zmm0. A loop over _Float16 arrays adding both products of each pair to a float accumulator, at -O2 with -march=x86-64-v4 -mavx10.2, does not use it: Clang splits the pairs with VPMOVDW and VPSRLD, widens them with VCVTPH2PSX, and adds the products with VMULPS, VFMADD231PS and VADDPS, which follow MXCSR. This site’s recorded cases include none of VDPPHPS.

Forms

Every encoding of VDPPHPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VDPPHPS xmm {k}{z}, xmm, xmm VDPPHPS_XMMf32_MASKmskw_XMM2f16_XMM2f16_AVX512EVEX.128.NP.0F38.W0 52 /rAVX10.2
VDPPHPS xmm {k}{z}, xmm, m128/m32bcst VDPPHPS_XMMf32_MASKmskw_XMM2f16_MEM2f16_AVX512EVEX.128.NP.0F38.W0 52 /rAVX10.2
VDPPHPS ymm {k}{z}, ymm, ymm VDPPHPS_YMMf32_MASKmskw_YMM2f16_YMM2f16_AVX512EVEX.256.NP.0F38.W0 52 /rAVX10.2
VDPPHPS ymm {k}{z}, ymm, m256/m32bcst VDPPHPS_YMMf32_MASKmskw_YMM2f16_MEM2f16_AVX512EVEX.256.NP.0F38.W0 52 /rAVX10.2
VDPPHPS zmm {k}{z}, zmm, zmm VDPPHPS_ZMMf32_MASKmskw_ZMM2f16_ZMM2f16_AVX512EVEX.512.NP.0F38.W0 52 /rAVX10.2
VDPPHPS zmm {k}{z}, zmm, m512/m32bcst VDPPHPS_ZMMf32_MASKmskw_ZMM2f16_MEM2f16_AVX512EVEX.512.NP.0F38.W0 52 /rAVX10.2

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 halves are combined into one single and added to the destination's old value.
VDPPHPS: groups of 2 elementsResult single i comes from halves 2i to 2i+1 of xmm2 and xmm3. Result singles 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 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 single i comes from halves 2i to 2i+1 of xmm2 and xmm3. Result singles 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):
    if k1[i]:
        x = zmm1.f32[i]
        a = zmm2.f16[2 * i + 1]
        b = src3.f16[2 * i + 1]
        x = fmadd_ne(a, b, x)
        a = zmm2.f16[2 * i]
        b = src3.f16[2 * i]
        zmm1.f32[i] = fmadd_ne(a, b, x)
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# FP16 inputs taken exactly; each sum to nearest even, single denormals flushed, no flags
# m32bcst: src3.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Not run on a processor: none of these processors has AVX10.2.

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
VDPPHPS xmm {k}{z}, xmm, xmm/m128/m32bcst VDPPHPS ymm {k}{z}, ymm, ymm/m256/m32bcst VDPPHPS 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.

All forms
AVX512-E4

Attributes

What else XED records about the forms. How to read.

All forms
write masking; always rounds to nearest even; denormal results flushed to zero
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VDPPHPS, 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_dpph_ps __m128 _mm_dpph_ps(__m128 __W, __m128h __A, __m128h __B)

VDPPHPS xmm, xmm, xmm EVEX.128 -mavx10.2

_mm_mask_dpph_ps __m128 _mm_mask_dpph_ps(__m128 __W, __mmask8 __U, __m128h __A, __m128h __B)

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

_mm_maskz_dpph_ps __m128 _mm_maskz_dpph_ps(__mmask8 __U, __m128 __W, __m128h __A, __m128h __B)

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

_mm256_dpph_ps __m256 _mm256_dpph_ps(__m256 __W, __m256h __A, __m256h __B)

VDPPHPS ymm, ymm, ymm EVEX.256 -mavx10.2

_mm256_mask_dpph_ps __m256 _mm256_mask_dpph_ps(__m256 __W, __mmask8 __U, __m256h __A, __m256h __B)

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

_mm256_maskz_dpph_ps __m256 _mm256_maskz_dpph_ps(__mmask8 __U, __m256 __W, __m256h __A, __m256h __B)

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

_mm512_dpph_ps __m512 _mm512_dpph_ps(__m512 __W, __m512h __A, __m512h __B)

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

_mm512_mask_dpph_ps __m512 _mm512_mask_dpph_ps(__m512 __W, __mmask16 __U, __m512h __A, __m512h __B)

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

_mm512_maskz_dpph_ps __m512 _mm512_maskz_dpph_ps(__mmask16 __U, __m512 __W, __m512h __A, __m512h __B)

VDPPHPS 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
AVX512_VNNI_FP16_128

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

Nova Lake, Diamond Rapids
AVX512_VNNI_FP16_256
Same as AVX512_VNNI_FP16_128Same as AVX512_VNNI_FP16_128
AVX512_VNNI_FP16_512
Same as AVX512_VNNI_FP16_128Same as AVX512_VNNI_FP16_128

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 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.