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

VDPBF16PS is the dot-product step for bfloat16 data. Each doubleword of the two sources holds a pair of bfloat16 values; the instruction multiplies the pairs element by element and adds both products to the single-precision accumulator in the destination. A bfloat16 value is the upper half of a single, with the same 8-bit exponent and a 7-bit fraction. 16 pairs fit a ZMM register, which keeps 16 sums. Its integer relatives are VPDPWSSD and VPDPBUSD.

Fixed arithmetic, no MXCSR

The instruction ignores MXCSR and never changes it: it rounds to nearest even, treats denormal inputs as zero, flushes denormal results to zero, and reports no exception, whatever the control bits say. Every recorded case on Zen 5 left MXCSR as it was, including one with every exception unmasked, where an overflow to infinity and -infinity + infinity, which gave a NaN, raised no #XM; and two products of about 7.3e-40 gave 0 with FTZ off.

The two products are added one at a time, each with its own rounding, the upper pair first. Two cases recorded on Zen 5 show it:

  • 1.0 + 2^-24 + 2^-24 gave 1.0, not 1 + 2^-23: each addition rounded the half-way result back to 1.0.
  • With products of -6.8e38 in the upper pair and +6.8e38 in the lower one, and an accumulator of 0, the result was -infinity: the first sum overflowed before the second was added.

Code that compares its results with a float loop must allow for both, and for the flushed denormals.

Feeding it

One way to produce the operands is VCVTNE2PS2BF16, which rounds two vectors of singles to bfloat16 and packs them into one register; Intel’s optimization manual uses it the same way to prepare bfloat16 inputs for AMX (Section 20.11.4, Example 20-23). Neither GCC 14 nor Clang 23 at -O2 with -march=znver5, whose Zen 5 target includes AVX512_BF16, turns a C loop over __bf16 arrays into VDPBF16PS, even with -ffast-math: Clang widens the values to floats by shifting them 16 bits left and uses VFMADD231PS, and GCC stays scalar. The intrinsics _mm512_dpbf16_ps and kin give the instruction in both. AMX’s TDPBF16PS does the same work on tiles.

Forms

Every encoding of VDPBF16PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VDPBF16PS xmm {k}{z}, xmm, xmm VDPBF16PS_XMMf32_MASKmskw_XMMu32_XMMu32_AVX512EVEX.128.F3.0F38.W0 52 /rAVX10.1 or AVX512_BF16
VDPBF16PS xmm {k}{z}, xmm, m128/m32bcst VDPBF16PS_XMMf32_MASKmskw_XMMu32_MEMu32_AVX512EVEX.128.F3.0F38.W0 52 /rAVX10.1 or AVX512_BF16
VDPBF16PS ymm {k}{z}, ymm, ymm VDPBF16PS_YMMf32_MASKmskw_YMMu32_YMMu32_AVX512EVEX.256.F3.0F38.W0 52 /rAVX10.1 or AVX512_BF16
VDPBF16PS ymm {k}{z}, ymm, m256/m32bcst VDPBF16PS_YMMf32_MASKmskw_YMMu32_MEMu32_AVX512EVEX.256.F3.0F38.W0 52 /rAVX10.1 or AVX512_BF16
VDPBF16PS zmm {k}{z}, zmm, zmm VDPBF16PS_ZMMf32_MASKmskw_ZMMu32_ZMMu32_AVX512EVEX.512.F3.0F38.W0 52 /rAVX10.1 or AVX512_BF16
VDPBF16PS zmm {k}{z}, zmm, m512/m32bcst VDPBF16PS_ZMMf32_MASKmskw_ZMMu32_MEMu32_AVX512EVEX.512.F3.0F38.W0 52 /rAVX10.1 or AVX512_BF16

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 {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
xmm {k}{z}, xmm, m128/m32bcstymm {k}{z}, ymm, m256/m32bcstzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512/m32bcst
Skylake-SP4 / 0.5p0110 / 0.5p0111 / 0.5p014 / 0.5p0511 / 0.5p05
Sapphire Rapids8 / 2p01515 / 2p01516 / 2p0158 / 2p0516 / 2p05
Zen 46 / 31FP2 FP311 / 0.5FP0 FP111 / 0.5FP0 FP16 / 3FP2 FP311 / 1FP0 FP1
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 1119; AMD 58455, row 949).

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 bfloat16s are combined into one single and added to the destination's old value.
VDPBF16PS: groups of 2 elementsResult single i comes from bfloat16s 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 bfloat16s 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.bf16[2 * i + 1]
        b = src3.bf16[2 * i + 1]
        x = fmadd_ne(a, b, x)
        a = zmm2.bf16[2 * i]
        b = src3.bf16[2 * i]
        zmm1.f32[i] = fmadd_ne(a, b, x)
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# BF16: to nearest even, denormals flushed, no flags; MXCSR unused
# m32bcst: src3.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 31 cases.

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
VDPBF16PS xmm {k}{z}, xmm, xmm/m128/m32bcst VDPBF16PS ymm {k}{z}, ymm, ymm/m256/m32bcst VDPBF16PS 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
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VDPBF16PS, 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_dpbf16_ps __m128 _mm_dpbf16_ps(__m128 __D, __m128bh __A, __m128bh __B)

VDPBF16PS xmm, xmm, xmm EVEX.128 -mavx512vl -mavx512bf16

_mm_mask_dpbf16_ps __m128 _mm_mask_dpbf16_ps(__m128 __D, __mmask8 __U, __m128bh __A, __m128bh __B)

VDPBF16PS xmm {k}, xmm, xmm EVEX.128 -mavx512vl -mavx512bf16

_mm_maskz_dpbf16_ps __m128 _mm_maskz_dpbf16_ps(__mmask8 __U, __m128 __D, __m128bh __A, __m128bh __B)

VDPBF16PS xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl -mavx512bf16

_mm256_dpbf16_ps __m256 _mm256_dpbf16_ps(__m256 __D, __m256bh __A, __m256bh __B)

VDPBF16PS ymm, ymm, ymm EVEX.256 -mavx512vl -mavx512bf16

_mm256_mask_dpbf16_ps __m256 _mm256_mask_dpbf16_ps(__m256 __D, __mmask8 __U, __m256bh __A, __m256bh __B)

VDPBF16PS ymm {k}, ymm, ymm EVEX.256 -mavx512vl -mavx512bf16

_mm256_maskz_dpbf16_ps __m256 _mm256_maskz_dpbf16_ps(__mmask8 __U, __m256 __D, __m256bh __A, __m256bh __B)

VDPBF16PS ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl -mavx512bf16

_mm512_dpbf16_ps __m512 _mm512_dpbf16_ps(__m512 __D, __m512bh __A, __m512bh __B)

VDPBF16PS zmm, zmm, zmm EVEX.512 -mavx512bf16

_mm512_mask_dpbf16_ps __m512 _mm512_mask_dpbf16_ps(__m512 __D, __mmask16 __U, __m512bh __A, __m512bh __B)

VDPBF16PS zmm {k}, zmm, zmm EVEX.512 -mavx512bf16

_mm512_maskz_dpbf16_ps __m512 _mm512_maskz_dpbf16_ps(__mmask16 __U, __m512 __D, __m512bh __A, __m512bh __B)

VDPBF16PS zmm {k}{z}, zmm, zmm EVEX.512 -mavx512bf16

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_BF16_128

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

or

AVX512_BF16
CPUID.(EAX=07H,ECX=1):EAX[5] AVX512_BF16

XED and Intel’s SDM differ: In the alternative without AVX10.1, XED asks for the AVX512_BF16 bit, CPUID.07H.01H:EAX[5], alone at every vector length. Revision 093 of Intel’s SDM pairs it with AVX512VL, CPUID.07H.00H:EBX[31], for xmm and ymm registers and with AVX512F, CPUID.07H.00H:EBX[16], for zmm registers; for the AVX10.1 alternative the two agree.

Sources: Intel XED v2026.08.23, datafiles/avx512-bf16/cpuid.xed.txt; Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026), VCVTNE2PS2BF16, VCVTNEPS2BF16 and VDPBF16PS: the opcode tables, pages 5-32, 5-38 and 5-160.

Nova Lake, Cooper Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512_BF16_256
Same as AVX512_BF16_128

XED and Intel’s SDM differ: see the note on AVX512_BF16_128.

Same as AVX512_BF16_128
AVX512_BF16_512
Same as AVX512_BF16_128

XED and Intel’s SDM differ: see the note on AVX512_BF16_128.

Same as AVX512_BF16_128

More AVX10.1 instructions

All 686 AVX10.1 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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-160 (VDPBF16PS)
  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.