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

VCVTNEPS2BF16 rounds each single of a register or of memory to bfloat16, the upper 16 bits of a single, and packs the results into the low half of the destination: 4 singles of an XMM source become 4 words of an XMM register, 8 of a YMM source fill an XMM register and 16 of a ZMM source a YMM one, and the bits above are cleared. It is the one-source form of VCVTNE2PS2BF16, whose page covers the fixed rounding: to nearest even whatever MXCSR says, denormal inputs as zeros of their sign, NaNs made quiet, MXCSR neither read nor written. It has two encodings: the EVEX one of AVX512_BF16, with a write mask and a broadcast, and a VEX one at 128 and 256 bits from AVX-NE-CONVERT, which the assembler marks {vex}.

Recorded on Zen 5

The 31 cases, all EVEX, agree with the SDM’s conversion routine, which adds 7FFFh plus the lowest kept bit to the single and keeps the upper half.

  • Ties. 3F808000h gave 3F80h and 3F818000h gave 3F82h, each to the even neighbor, and 3F80C000h, above the tie, gave 3F81h.
  • Overflow. 7F7F8000h, a tie below infinity, gave 7F80h, as did the largest single, while 7F7F0000h stayed 7F7Fh.
  • Exceptions. With MXCSR 0, every exception unmasked, the signaling NaN 7F812345h gave 7FC1h without a fault, and MXCSR stayed 0.
  • Masks. Zeroing masking cleared the words left out, and a broadcast of 3F818000h gave 3F82h in every word selected.

In compiled code

At -O2 with -march=znver5, Clang 23 converts float to __bf16 with VCVTNEPS2BF16, one value or, in a loop, 8 at a time from YMM registers; with -mavxneconvert it uses the VEX form. GCC 14 calls __truncsfbf2 for each element in every case, and emits the instruction only for intrinsics such as _mm512_cvtneps_pbh. The two differ on denormals: 007FC000h gives 0 here, where an exact rounding gives 0080h, the smallest normal bfloat16.

AMD’s Zen 5 latency spreadsheet gives the XMM source one macro-op on pipe FP2 or FP3 and 3 cycles, and the YMM and ZMM sources two macro-ops with 6 and 7 cycles.

Forms

Every encoding of VCVTNEPS2BF16 that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTNEPS2BF16 xmm, xmm VCVTNEPS2BF16_XMMbf16_XMMf32VEX.128.F3.0F38.W0 72 /rAVX_NE_CONVERT
VCVTNEPS2BF16 xmm, m128 VCVTNEPS2BF16_XMMbf16_MEMf32_VL128VEX.128.F3.0F38.W0 72 /rAVX_NE_CONVERT
VCVTNEPS2BF16 xmm, ymm VCVTNEPS2BF16_XMMbf16_YMMf32VEX.256.F3.0F38.W0 72 /rAVX_NE_CONVERT
VCVTNEPS2BF16 xmm, m256 VCVTNEPS2BF16_XMMbf16_MEMf32_VL256VEX.256.F3.0F38.W0 72 /rAVX_NE_CONVERT
VCVTNEPS2BF16 xmm {k}{z}, xmm VCVTNEPS2BF16_XMMbf16_MASKmskw_XMMf32_AVX512EVEX.128.F3.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNEPS2BF16 xmm {k}{z}, m128/m32bcst VCVTNEPS2BF16_XMMbf16_MASKmskw_MEMf32_AVX512_VL128EVEX.128.F3.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNEPS2BF16 xmm {k}{z}, ymm VCVTNEPS2BF16_XMMbf16_MASKmskw_YMMf32_AVX512EVEX.256.F3.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNEPS2BF16 xmm {k}{z}, m256/m32bcst VCVTNEPS2BF16_XMMbf16_MASKmskw_MEMf32_AVX512_VL256EVEX.256.F3.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNEPS2BF16 ymm {k}{z}, zmm VCVTNEPS2BF16_YMMbf16_MASKmskw_ZMMf32_AVX512EVEX.512.F3.0F38.W0 72 /rAVX10.1 or AVX512_BF16
VCVTNEPS2BF16 ymm {k}{z}, m512/m32bcst VCVTNEPS2BF16_YMMbf16_MASKmskw_MEMf32_AVX512_VL512EVEX.512.F3.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, xmmxmm, m128xmm, ymmxmm, m256xmm {k}{z}, xmmno maskxmm {k}{z}, xmmwith a mask, zeroingxmm {k}{z}, m128/m32bcstno mask, broadcastxmm {k}{z}, m128/m32bcstwith a mask, zeroingxmm {k}{z}, ymmno maskxmm {k}{z}, ymmwith a mask, zeroingxmm {k}{z}, m256/m32bcstno mask, broadcastxmm {k}{z}, m256/m32bcstwith a mask, zeroingymm {k}{z}, zmmno maskymm {k}{z}, zmmwith a mask, zeroingymm {k}{z}, m512/m32bcstno mask, broadcastymm {k}{z}, m512/m32bcstwith a mask, zeroing
Skylake-SP5 / 1p0155 / 1p0159 / 1p0159 / 1p0157 / 1p0157 / 1p01514 / 1p01514 / 1p0157 / 1p057 / 1p0514 / 1p0514 / 1p05
Sapphire Rapids8 / 1p01510 / 1p01515 / 1p01517 / 1p0158 / 1p01510 / 1p01516 / 1p01518 / 1p0158 / 2p0510 / 2p0516 / 2p0518 / 2p05
Lunar Lake5 / 0.5V0 V1 V2 V35 / 0.5V0 V1 V2 V37 / 2V0 V1 V2 V37 / 2V0 V1 V2 V3
Zen 43 / 0.5FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP310 / 0.5FP2 FP36 / 1FP2 FP36 / 1FP2 FP313 / 1FP2 FP313 / 1FP2 FP36 / 2FP2 FP36 / 2FP2 FP313 / 2FP2 FP313 / 2FP2 FP3

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.

Narrow: each single becomes a bfloat16, in the same order, at the low end of the result.
VCVTNEPS2BF16: each element narrowedResult bfloat16s 15 to 0: a15, unchanged (bit 14 of k1 is 0), a13, a12, a11, a10, a9, a8, a7, a6, a5, a4, a3, a2, a1, a0.0123456789101112131415zmm2or m512a1111111111111110k1a0a1a2a3a4a5a6a7a8a9a10a11a12a13a15ymm1

Shown for the zmm form; the xmm and ymm forms work the same on 4 and 8 singles. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result bfloat16s 15 to 0: a15, unchanged (bit 14 of k1 is 0), a13, a12, a11, a10, a9, a8, a7, a6, a5, a4, a3, a2, a1, a0.

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]:  # 1 without a write mask
        a = src2.f32[i]
        ymm1.bf16[i] = to_bf16_ne(a)
    elif zeroing:
        ymm1.bf16[i] = 0
    # else: ymm1.bf16[i] keeps its value
for i in range(VL // 32, 8):
    ymm1.w[i] = 0
# m32bcst: src2.f32[i] is the m32 for every i
# BF16: to nearest even, denormals flushed, no flags; MXCSR unused
# ymm1 is zeroed from bit 128 (xmm) or 256 (ymm) up

Run on AMD Zen 5 (EPYC 9645): 31 cases. The AVX-NE-CONVERT forms were not run: none of these processors has AVX-NE-CONVERT.

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
VCVTNEPS2BF16 xmm, xmm/m128 VCVTNEPS2BF16 xmm, ymm/m256
xmmexplicitwrite
xmm/m128, ymm/m256explicitread
VCVTNEPS2BF16 xmm {k}{z}, xmm/m128/m32bcst VCVTNEPS2BF16 xmm {k}{z}, ymm/m256/m32bcst VCVTNEPS2BF16 ymm {k}{z}, zmm/m512/m32bcst
xmm, ymmexplicitwrite (masked)
{k}explicitread (write mask)
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
VEX forms
always rounds to nearest even; denormal inputs read as zero; denormal results flushed to zero
EVEX memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTNEPS2BF16, 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_cvtneps_avx_pbh __m128bh _mm_cvtneps_avx_pbh(__m128 __A)

VCVTNEPS2BF16 xmm, xmm VEX.128 -mavxneconvert

_mm_cvtneps_pbh __m128bh _mm_cvtneps_pbh(__m128 A)

VCVTNEPS2BF16 xmm, xmm EVEX.128 -mavx512vl -mavx512bf16

_mm_mask_cvtneps_pbh __m128bh _mm_mask_cvtneps_pbh(__m128bh __W, __mmask8 __U, __m128 __A)

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

_mm_maskz_cvtneps_pbh __m128bh _mm_maskz_cvtneps_pbh(__mmask8 __U, __m128 __A)

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

_mm256_cvtneps_avx_pbh __m128bh _mm256_cvtneps_avx_pbh(__m256 __A)

VCVTNEPS2BF16 xmm, ymm VEX.256 -mavxneconvert

_mm256_cvtneps_pbh __m128bh _mm256_cvtneps_pbh(__m256 A)

VCVTNEPS2BF16 xmm, ymm EVEX.256 -mavx512vl -mavx512bf16

_mm256_mask_cvtneps_pbh __m128bh _mm256_mask_cvtneps_pbh(__m128bh __W, __mmask8 __U, __m256 __A)

VCVTNEPS2BF16 xmm {k}, ymm EVEX.256 -mavx512vl -mavx512bf16

_mm256_maskz_cvtneps_pbh __m128bh _mm256_maskz_cvtneps_pbh(__mmask8 __U, __m256 __A)

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

_mm512_cvtneps_pbh __m256bh _mm512_cvtneps_pbh(__m512 __A)

VCVTNEPS2BF16 ymm, zmm EVEX.512 -mavx512bf16

_mm512_mask_cvtneps_pbh __m256bh _mm512_mask_cvtneps_pbh(__m256bh __W, __mmask16 __U, __m512 __A)

VCVTNEPS2BF16 ymm {k}, zmm EVEX.512 -mavx512bf16

_mm512_maskz_cvtneps_pbh __m256bh _mm512_maskz_cvtneps_pbh(__mmask16 __U, __m512 __A)

VCVTNEPS2BF16 ymm {k}{z}, 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
AVX_NE_CONVERT

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

Arrow Lake, Panther Lake, Nova Lake, Diamond Rapids, Sierra Forest, Clearwater Forest, Zen 6
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 AVX-NE-CONVERT instructions

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