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

VCVTPS2PHX narrows singles to half precision: four from an XMM register into the low 64 bits of an XMM register, eight from a YMM register, sixteen from a ZMM register into a YMM register, with the rest of the destination cleared. It converts as VCVTPS2PH does, rounding to the 11 significant bits of a half, but its encoding is that of the other AVX512-FP16 arithmetic, opcode 1Dh in EVEX map 5 with the 66 prefix.

Next to VCVTPS2PH

  • Rounding. There is no immediate: VCVTPS2PHX rounds by MXCSR.RC, or by {er} on the 512-bit register form, as VADDPH does. _mm512_cvtx_roundps_ph(x, _MM_FROUND_TO_ZERO | _MM_FROUND_NO_EXC) becomes vcvtps2phx ymm0, zmm0, {rz-sae} in GCC 14 and Clang 23, where _mm512_cvtps_ph(x, _MM_FROUND_TO_ZERO) is VCVTPS2PH with immediate 3.
  • Broadcast, but no store. The source can be one single broadcast from memory; the destination is always a register, so the masked store to memory of VCVTPS2PH has no counterpart.
  • MXCSR. Intel’s entry says that DAZ applies to the single inputs, and that the half results are never flushed: a result below the smallest normal half is a denormal whatever FTZ says, as for VCVTPS2PH. DE is listed only when DAZ is clear.

In our builds

At -O2 with -march=x86-64-v4 -mavx512fp16, a loop h[i] = f[i] narrowing a float array to _Float16 becomes VCVTPS2PHX in both compilers, with the source in memory and a separate store: GCC joins two YMM results with VINSERTI64X4 for one ZMM store, Clang stores XMM results. With only F16C, Clang used VCVTPS2PH with a memory destination, as its page shows. A single float is narrowed with VCVTSS2SH, and VCVTPH2PSX is the way back. AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VCVTPS2PHX.

Forms

Every encoding of VCVTPS2PHX that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTPS2PHX xmm {k}{z}, xmm VCVTPS2PHX_XMMf16_MASKmskw_XMMf32_AVX512EVEX.128.66.MAP5.W0 1D /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPS2PHX xmm {k}{z}, m128/m32bcst VCVTPS2PHX_XMMf16_MASKmskw_MEMf32_AVX512_VL128EVEX.128.66.MAP5.W0 1D /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPS2PHX xmm {k}{z}, ymm VCVTPS2PHX_XMMf16_MASKmskw_YMMf32_AVX512EVEX.256.66.MAP5.W0 1D /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPS2PHX xmm {k}{z}, m256/m32bcst VCVTPS2PHX_XMMf16_MASKmskw_MEMf32_AVX512_VL256EVEX.256.66.MAP5.W0 1D /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPS2PHX ymm {k}{z}, zmm, {er} VCVTPS2PHX_YMMf16_MASKmskw_ZMMf32_AVX512EVEX.512.66.MAP5.W0 1D /rAVX10.1 or AVX512_FP16
VCVTPS2PHX ymm {k}{z}, m512/m32bcst VCVTPS2PHX_YMMf16_MASKmskw_MEMf32_AVX512_VL512EVEX.512.66.MAP5.W0 1D /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}, m128/m32bcstno mask, broadcastxmm {k}{z}, m128/m32bcstwith a mask, zeroing
xmm {k}{z}, m256/m32bcstno mask, broadcast
xmm {k}{z}, ymmno maskxmm {k}{z}, ymmwith a mask, zeroingxmm {k}{z}, m256/m32bcstwith a mask, zeroingymm {k}{z}, zmm, {er}no mask, with {er}ymm {k}{z}, zmm, {er}with a mask, zeroingymm {k}{z}, m512/m32bcstno mask, broadcastymm {k}{z}, m512/m32bcstwith a mask, zeroing
Sapphire Rapids6 / 1p0159 / 1p01514 / 1p01516 / 1p0158 / 1p01511 / 1p01518 / 1p0158 / 1p0511 / 1p0516 / 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.

Narrow: each single becomes a half, in the same order, at the low end of the result.
VCVTPS2PHX: each element narrowedResult halves 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 forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result halves 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]:
        ymm1.f16[i] = to_f16(src2.f32[i])
    elif zeroing:
        ymm1.f16[i] = 0
    # else: ymm1.f16[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
# {er}: the form's rounding, not MXCSR.RC, and no flags
# ymm1 is zeroed from bit 128 (xmm) or 256 (ymm) 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
VCVTPS2PHX xmm {k}{z}, xmm/m128/m32bcst VCVTPS2PHX xmm {k}{z}, ymm/m256/m32bcst VCVTPS2PHX ymm {k}{z}, zmm/m512/m32bcst, {er}
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.

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 Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTPS2PHX, 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_cvtxps_ph __m128h _mm_cvtxps_ph(__m128 __A)

VCVTPS2PHX xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

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

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

_mm_maskz_cvtxps_ph __m128h _mm_maskz_cvtxps_ph(__mmask8 __U, __m128 __A)

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

_mm256_cvtxps_ph __m128h _mm256_cvtxps_ph(__m256 __A)

VCVTPS2PHX xmm, ymm EVEX.256 -mavx512fp16 -mavx512vl

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

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

_mm256_maskz_cvtxps_ph __m128h _mm256_maskz_cvtxps_ph(__mmask8 __U, __m256 __A)

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

_mm512_cvtx_roundps_ph __m256h _mm512_cvtx_roundps_ph(__m512 A, const int R)

VCVTPS2PHX ymm, zmm, {er} EVEX.512 -mavx512fp16

_mm512_cvtxps_ph __m256h _mm512_cvtxps_ph(__m512 __A)

VCVTPS2PHX ymm, zmm EVEX.512 -mavx512fp16

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

VCVTPS2PHX ymm {k}, zmm, {er} EVEX.512 -mavx512fp16

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

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

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

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

_mm512_maskz_cvtxps_ph __m256h _mm512_maskz_cvtxps_ph(__mmask16 __U, __m512 __A)

VCVTPS2PHX ymm {k}{z}, zmm 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-72 (VCVTPS2PHX)
  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.