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

VCVTPH2PSX widens half-precision values to singles: four from 64 bits into an XMM register, eight into a YMM register and sixteen into a ZMM register. It does what VCVTPH2PS does, and shares its entry in Intel’s manual: every half, denormals included, is exactly a single, so nothing is rounded and MXCSR.RC plays no part. The new encoding, opcode 13h in EVEX map 6 with the 66 prefix, where the EVEX VCVTPH2PS has the same byte in 0F38, adds one thing: a source of one half broadcast from memory to every element ({1to16} and so on). Intel’s optimization manual recommends it over the older form for that reason (Sections 18.5.6 and 18.5.7). VADDPH covers AVX512-FP16 and the format.

A different exception list

The shared entry gives VCVTPH2PSX the exceptions invalid and denormal, where VCVTPH2PS reports only invalid; the same entry says that for a denormal input VCVTPH2PS returns the normal result with DAZ ignored and no denormal exception. A program with the denormal exception unmasked can therefore see VCVTPH2PSX fault where VCVTPH2PS does not, as VCVTPH2PD’s page notes for the conversion to doubles. The 512-bit register form takes {sae}.

In our builds

At -O2 with -march=x86-64-v4 -mavx512fp16, GCC 14 and Clang 23 compile f[i] = h[i], from a _Float16 array to a float array, to VCVTPH2PSX, never VCVTPH2PS: GCC from ymm to zmm registers after a load, Clang from memory into ymm registers. _mm512_cvtxph_ps gives it too; a single value is converted with VCVTSH2SS. Without AVX512-FP16 the same loop uses VCVTPH2PS, as its page shows. AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VCVTPH2PSX.

Forms

Every encoding of VCVTPH2PSX that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTPH2PSX xmm {k}{z}, xmm VCVTPH2PSX_XMMf32_MASKmskw_XMMf16_AVX512EVEX.128.66.MAP6.W0 13 /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPH2PSX xmm {k}{z}, m64/m16bcst VCVTPH2PSX_XMMf32_MASKmskw_MEMf16_AVX512EVEX.128.66.MAP6.W0 13 /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPH2PSX ymm {k}{z}, xmm VCVTPH2PSX_YMMf32_MASKmskw_XMMf16_AVX512EVEX.256.66.MAP6.W0 13 /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPH2PSX ymm {k}{z}, m128/m16bcst VCVTPH2PSX_YMMf32_MASKmskw_MEMf16_AVX512EVEX.256.66.MAP6.W0 13 /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPH2PSX zmm {k}{z}, ymm, {sae} VCVTPH2PSX_ZMMf32_MASKmskw_YMMf16_AVX512EVEX.512.66.MAP6.W0 13 /rAVX10.1 or AVX512_FP16
VCVTPH2PSX zmm {k}{z}, m256/m16bcst VCVTPH2PSX_ZMMf32_MASKmskw_MEMf16_AVX512EVEX.512.66.MAP6.W0 13 /rAVX10.1 or AVX512_FP16

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}, xmmno maskxmm {k}{z}, xmmwith a mask, zeroingxmm {k}{z}, m64/m16bcstno mask, broadcastxmm {k}{z}, m64/m16bcstwith a mask, zeroing
ymm {k}{z}, m128/m16bcstno mask, broadcast
ymm {k}{z}, xmmno maskymm {k}{z}, xmmwith a mask, zeroingymm {k}{z}, m128/m16bcstwith a mask, zeroingzmm {k}{z}, ymm, {sae}no mask, with {sae}zmm {k}{z}, ymm, {sae}with a mask, zeroingzmm {k}{z}, m256/m16bcstno mask, broadcastzmm {k}{z}, m256/m16bcstwith a mask, zeroing
Sapphire Rapids6 / 1p0159 / 1p01512 / 1p01515 / 1p0158 / 1p01511 / 1p01518 / 1p0158 / 1p0511 / 1p0515 / 1p0518 / 1p05

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.

Widen: each half becomes a single, converted, in the same order.
VCVTPH2PSX: each element widenedResult singles 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.0123456789101112131415ymm2or m256a1111111111111110k1a0a1a2a3a4a5a6a7a8a9a10a11a12a13a15zmm1

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

Result singles 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]:
        zmm1.f32[i] = to_f32(src2.f16[i])
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# m16bcst: src2.f16[i] is the m16 for every i
# {sae}: no exception flags
# zmm1 is zeroed from bit VL up

Not run on a processor: none of these processors has AVX512-FP16. The tests check its arithmetic against MPFR.

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
VCVTPH2PSX xmm {k}{z}, xmm/m64/m16bcst VCVTPH2PSX ymm {k}{z}, xmm/m128/m16bcst VCVTPH2PSX zmm {k}{z}, ymm/m256/m16bcst, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m64/m16bcst, xmm/m128/m16bcst, ymm/m256/m16bcstexplicitread

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

Attributes

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

All forms
write masking; follows MXCSR
Memory forms
embedded broadcast (tuple Half); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTPH2PSX, 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_cvtxph_ps __m128 _mm_cvtxph_ps(__m128h __A)

VCVTPH2PSX xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_mask_cvtxph_ps __m128 _mm_mask_cvtxph_ps(__m128 __W, __mmask8 __U, __m128h __A)

VCVTPH2PSX xmm {k}, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_maskz_cvtxph_ps __m128 _mm_maskz_cvtxph_ps(__mmask8 __U, __m128h __A)

VCVTPH2PSX xmm {k}{z}, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm256_cvtxph_ps __m256 _mm256_cvtxph_ps(__m128h __A)

VCVTPH2PSX ymm, xmm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_mask_cvtxph_ps __m256 _mm256_mask_cvtxph_ps(__m256 __W, __mmask8 __U, __m128h __A)

VCVTPH2PSX ymm {k}, xmm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_maskz_cvtxph_ps __m256 _mm256_maskz_cvtxph_ps(__mmask8 __U, __m128h __A)

VCVTPH2PSX ymm {k}{z}, xmm EVEX.256 -mavx512fp16 -mavx512vl

_mm512_cvtx_roundph_ps __m512 _mm512_cvtx_roundph_ps(__m256h A, const int R)

VCVTPH2PSX zmm, ymm, {sae} EVEX.512 -mavx512fp16

_mm512_cvtxph_ps __m512 _mm512_cvtxph_ps(__m256h __A)

VCVTPH2PSX zmm, ymm EVEX.512 -mavx512fp16

_mm512_mask_cvtx_roundph_ps __m512 _mm512_mask_cvtx_roundph_ps(__m512 W, __mmask16 U, __m256h A, const int R)

VCVTPH2PSX zmm {k}, ymm, {sae} EVEX.512 -mavx512fp16

_mm512_mask_cvtxph_ps __m512 _mm512_mask_cvtxph_ps(__m512 __W, __mmask16 __U, __m256h __A)

VCVTPH2PSX zmm {k}, ymm EVEX.512 -mavx512fp16

_mm512_maskz_cvtx_roundph_ps __m512 _mm512_maskz_cvtx_roundph_ps(__mmask16 U, __m256h A, const int R)

VCVTPH2PSX zmm {k}{z}, ymm, {sae} EVEX.512 -mavx512fp16

_mm512_maskz_cvtxph_ps __m512 _mm512_maskz_cvtxph_ps(__mmask16 __U, __m256h __A)

VCVTPH2PSX zmm {k}{z}, ymm EVEX.512 -mavx512fp16

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_FP16_128

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

or

AVX512_FP16 + AVX512VL
CPUID.(EAX=07H,ECX=0):EDX[23] AVX512_FP16
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6
AVX512_FP16_256
Same as AVX512_FP16_128Same as AVX512_FP16_128
AVX512_FP16_512

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

or

AVX512_FP16
CPUID.(EAX=07H,ECX=0):EDX[23] AVX512_FP16

Same as AVX512_FP16_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-54 (VCVTPH2PS/VCVTPH2PSX)
  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.