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

VCVTNE2PS2BF16 rounds the singles of two registers to bfloat16 and packs them into one: the elements of the third operand fill the lower half of the result, those of the second operand the upper half. A bfloat16 is the upper 16 bits of a single, so the conversion keeps the 8-bit exponent and rounds the 23-bit fraction to 7 bits. It came with AVX512_BF16, with VCVTNEPS2BF16, which narrows one register into half of one, and VDPBF16PS, which multiplies the pairs it produces.

Which source goes low

In C, _mm512_cvtne2ps_pbh(a, b) puts the 16 values of b in the low 16 words and those of a above them: GCC 14 and Clang 23 at -O2 compile it to vcvtne2ps2bf16 zmm0, zmm0, zmm1 with a in zmm0. To narrow 32 consecutive floats in their order, the later 16 are the first argument. Intel’s optimization manual converts AMX results this way, two blocks of floats into whole 64-byte lines of bfloat16, passing the second block first (Section 20.11.4, Example 20-23). Unlike VPACKSSDW, the instruction does not interleave its sources by 128-bit lane, so no permute has to follow.

Neither compiler uses it for a plain loop: with -march=znver5, Clang 23 narrows an array of floats to __bf16 with the one-source VCVTNEPS2BF16, and GCC 14 calls the library routine __truncsfbf2 for each element.

Fixed rounding

The instruction never reads or writes MXCSR and raises no exception. Zen 5’s recorded cases show what that means:

  • It always rounds to nearest even: with MXCSR.RC set to round toward zero, 3F808000h (1 + 2^-8, a tie) gave 3F80h, and the largest single, 7F7FFFFFh, gave infinity, 7F80h.
  • Denormal inputs become zeros of their sign, with DAZ clear: 007FC000h, which would otherwise round to the smallest normal bfloat16, gave 0000h, and 80400000h gave 8000h.
  • NaNs come out quiet, keeping the top 7 bits of their fraction: the signaling NaN 7F812345h gave 7FC1h, and FF800001h, whose payload lies only in the dropped bits, gave FFC0h. With the invalid-operation exception unmasked, no #XM followed.

AMD’s Zen 5 guide lists the xmm form as one macro-op with a latency of 3 cycles, and the ymm and zmm forms as two, with 6 and 7.

Forms

Every encoding of VCVTNE2PS2BF16 that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTNE2PS2BF16 xmm {k}{z}, xmm, xmm VCVTNE2PS2BF16_XMMbf16_MASKmskw_XMMf32_XMMf32_AVX512EVEX.128.F2.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNE2PS2BF16 xmm {k}{z}, xmm, m128/m32bcst VCVTNE2PS2BF16_XMMbf16_MASKmskw_XMMf32_MEMf32_AVX512_VL128EVEX.128.F2.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNE2PS2BF16 ymm {k}{z}, ymm, ymm VCVTNE2PS2BF16_YMMbf16_MASKmskw_YMMf32_YMMf32_AVX512EVEX.256.F2.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNE2PS2BF16 ymm {k}{z}, ymm, m256/m32bcst VCVTNE2PS2BF16_YMMbf16_MASKmskw_YMMf32_MEMf32_AVX512_VL256EVEX.256.F2.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNE2PS2BF16 zmm {k}{z}, zmm, zmm VCVTNE2PS2BF16_ZMMbf16_MASKmskw_ZMMf32_ZMMf32_AVX512EVEX.512.F2.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNE2PS2BF16 zmm {k}{z}, zmm, m512/m32bcst VCVTNE2PS2BF16_ZMMbf16_MASKmskw_ZMMf32_MEMf32_AVX512_VL512EVEX.512.F2.0F38.W0 72 /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, xmmno maskxmm {k}{z}, xmm, xmmwith a mask, zeroingxmm {k}{z}, xmm, m128/m32bcstno mask, broadcastxmm {k}{z}, xmm, m128/m32bcstwith a mask, zeroingymm {k}{z}, ymm, ymmno maskymm {k}{z}, ymm, ymmwith a mask, zeroingymm {k}{z}, ymm, m256/m32bcstno mask, broadcastymm {k}{z}, ymm, m256/m32bcstwith a mask, zeroingzmm {k}{z}, zmm, zmmno maskzmm {k}{z}, zmm, zmmwith a mask, zeroingzmm {k}{z}, zmm, m512/m32bcstno mask, broadcastzmm {k}{z}, zmm, m512/m32bcstwith a mask, zeroing
Skylake-SP5 / 1p0155 / 1p0159 / 1p0159 / 1p0157 / 1p0157 / 1p01514 / 1p01514 / 1p0157 / 1p057 / 1p0514 / 1p0514 / 1p05
Sapphire Rapids8 / 1.33p01510 / 1.33p01515 / 1.33p01517 / 1.33p0158 / 1.33p01510 / 1.33p01516 / 1.33p01518 / 1.33p0158 / 2p0510 / 2p0516 / 2p0518 / 2p05
Zen 43 / 0.5FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP310 / 0.5FP2 FP36 / 1FP2 FP36 / 1FP2 FP313 / 1FP2 FP313 / 1FP2 FP36 / 21FP2 FP36 / 21FP2 FP313 / 2FP2 FP313 / 2FP2 FP3
  1. Zen 4 model: AMD's spreadsheets give latency 7 for Zen 4 and Zen 5 (AMD 57647, row 977; AMD 58455, row 945).

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.

Two sources narrowed into one: the singles of ymm3 fill the low half of the result, those of ymm2 the high half.
VCVTNE2PS2BF16: two sources narrowed into oneResult bfloat16s 15 to 0: a7, unchanged (bit 14 of k1 is 0), a5, a4, a3, a2, a1, a0, b7, b6, b5, b4, b3, b2, b1, b0.01234567ymm2a1111111111111110k1b0b1b2b3b4b5b6b7a0a1a2a3a4a5a7ymm101234567ymm3or m256b

Shown for the ymm form; the xmm and zmm forms work the same on 8 and 32 singles. 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 single from memory stands for every element of ymm3.

Result bfloat16s 15 to 0: a7, unchanged (bit 14 of k1 is 0), a5, a4, a3, a2, a1, a0, b7, b6, b5, b4, b3, b2, b1, b0.

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 // 16):
    if k1[i]:
        if i < VL // 32:
            x = src3.f32[i]
        else:
            x = zmm2.f32[i - VL // 32]
        zmm1.bf16[i] = to_bf16_ne(x)
    elif zeroing:
        zmm1.bf16[i] = 0
    # else: zmm1.bf16[i] keeps its value
# m32bcst: src3.f32[i] is the m32 for every i
# BF16: to nearest even, denormals flushed, no flags; MXCSR unused
# 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
VCVTNE2PS2BF16 xmm {k}{z}, xmm, xmm/m128/m32bcst VCVTNE2PS2BF16 ymm {k}{z}, ymm, ymm/m256/m32bcst VCVTNE2PS2BF16 zmm {k}{z}, zmm, zmm/m512/m32bcst
xmm, ymm, zmmexplicitwrite (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)

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTNE2PS2BF16, 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_cvtne2ps_pbh __m128bh _mm_cvtne2ps_pbh(__m128 __A, __m128 __B)

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

_mm_mask_cvtne2ps_pbh __m128bh _mm_mask_cvtne2ps_pbh(__m128bh __W, __mmask8 __U, __m128 __A, __m128 __B)

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

_mm_maskz_cvtne2ps_pbh __m128bh _mm_maskz_cvtne2ps_pbh(__mmask8 __U, __m128 __A, __m128 __B)

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

_mm256_cvtne2ps_pbh __m256bh _mm256_cvtne2ps_pbh(__m256 __A, __m256 __B)

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

_mm256_mask_cvtne2ps_pbh __m256bh _mm256_mask_cvtne2ps_pbh(__m256bh __W, __mmask16 __U, __m256 __A, __m256 __B)

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

_mm256_maskz_cvtne2ps_pbh __m256bh _mm256_maskz_cvtne2ps_pbh(__mmask16 __U, __m256 __A, __m256 __B)

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

_mm512_cvtne2ps_pbh __m512bh _mm512_cvtne2ps_pbh(__m512 __A, __m512 __B)

VCVTNE2PS2BF16 zmm, zmm, zmm EVEX.512 -mavx512bf16

_mm512_mask_cvtne2ps_pbh __m512bh _mm512_mask_cvtne2ps_pbh(__m512bh __W, __mmask32 __U, __m512 __A, __m512 __B)

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

_mm512_maskz_cvtne2ps_pbh __m512bh _mm512_maskz_cvtne2ps_pbh(__mmask32 __U, __m512 __A, __m512 __B)

VCVTNE2PS2BF16 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-32 (VCVTNE2PS2BF16)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  8. Software Optimization Guide for the AMD Zen5 Microarchitecture (58455, rev. 1.00, August 2024), Wayback Machine copy of AMD's ZIP

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.