Extensions
Forms
2 (2 VEX)
Data
Intel XED v2026.08.23

VCVTNEOBF162PS reads 128 or 256 bits of bfloat16 values from memory and widens the odd-numbered ones, elements 1, 3, 5 and so on, to singles: each doubleword of the destination gets the high word of the matching doubleword in memory. It is the other half of VCVTNEEBF162PS, whose page covers what the two share: the source is always memory, which Crestmont widens in its load pipelines; the conversion is exact and puts the 16 bits above 16 zeros, so denormals and signaling NaNs come through as they are; no exception, no MXCSR; and the bits above the vector are cleared.

The cheapest of the four

For an odd element the bfloat16 value already sits in the upper half of its doubleword, so the single it becomes is that doubleword with its low 16 bits cleared, an AND with FFFF0000h on each element. A loop summing pairs, o[i] = (float)b[2*i] + (float)b[2*i+1], shows both halves in our builds: Clang 23 at -O2 with -mavxneconvert gets the even elements with VPSLLD by 16 and the odd ones with a VPBLENDW against zero, from ordinary loads, and does not use this instruction; GCC 14 calls __extendbfsf2 for each element. What the instruction saves is the separate ALU step, done in the load instead.

The encoding is VEX.F2.0F38.W0 B0, at 128 and 256 bits, and the intrinsics are _mm_cvtneobf16_ps and _mm256_cvtneobf16_ps, which take a pointer; GCC 14 and Clang 23 compile them with -mavxneconvert to the instruction with that pointer as its operand. Zen 5 lacks AVX-NE-CONVERT.

In the optimization guide

What the optimization guide says about VCVTNEOBF162PS, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Crestmont and Gracemont

  • Vectors and AVX2: Crestmont widens BF16 and FP16 to single precision in the load pipelines, using no vector port.

Forms

Every encoding of VCVTNEOBF162PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTNEOBF162PS xmm, m128 VCVTNEOBF162PS_XMMf32_MEM2bf16VEX.128.F2.0F38.W0 B0 /rAVX_NE_CONVERT
VCVTNEOBF162PS ymm, m256 VCVTNEOBF162PS_YMMf32_MEM2bf16VEX.256.F2.0F38.W0 B0 /rAVX_NE_CONVERT

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, m128ymm, m256
Lunar Lake5 / 0.5V0 V1 V2 V37 / 2V0 V1 V2 V3

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.

The odd bfloat16s only: bfloat16s 3 and 1 of the source make singles 1 and 0 of the result, and so on.
VCVTNEOBF162PS: the odd elementsResult single i comes from bfloat16 2i+1 of m128. Result singles 3 to 0: a7, a5, a3, a1.02461357m128aa1a3a5a7xmm1

The ymm form repeats this in each 128-bit lane.

Result single i comes from bfloat16 2i+1 of m128. Result singles 3 to 0: a7, a5, a3, a1.

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):
    a = mem.bf16[2 * i + 1]
    ymm1.f32[i] = to_f32_ne(a)
# ymm1 is zeroed from bit VL up

Not run on a processor: 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
VCVTNEOBF162PS xmm, m128 VCVTNEOBF162PS ymm, m256
xmm, ymmexplicitwrite
m128/256explicitread

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
avx-type-4

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTNEOBF162PS, 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_cvtneobf16_ps __m128 _mm_cvtneobf16_ps(const __m128bh *__A)

VCVTNEOBF162PS xmm, m128 VEX.128 -mavxneconvert

_mm256_cvtneobf16_ps __m256 _mm256_cvtneobf16_ps(const __m256bh *__A)

VCVTNEOBF162PS ymm, m256 VEX.256 -mavxneconvert

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

More AVX-NE-CONVERT 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-36 (VCVTNEOBF162PS)
  6. 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.