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

VCVTPH2PS widens half-precision values (IEEE 754’s binary16: a sign, 5 exponent bits and 10 fraction bits) to singles: four from the low 64 bits of an XMM register or from memory, or eight into a YMM register. Every half, denormals included, has an exact single, so nothing is rounded and the result never depends on MXCSR.RC. It came with F16C (CPUID.01H:ECX[29]), which has only this conversion and VCVTPS2PH back: on such processors halves are a storage format, widened before any arithmetic. Intel’s optimization manual weighs the memory and bandwidth such data saves against the cost of converting it (Section 15.14).

Denormals and NaNs

Intel’s and AMD’s manuals both say that a denormal half converts to its normal single value with MXCSR.DAZ ignored and no denormal exception. AMD’s exception table for the instruction nonetheless lists the denormal flag, with overflow, underflow and precision. The cases recorded on Zen 5 follow the text: with DAZ set, the smallest denormal half 0001h became 2^-24 (33800000h), and no flag but IE was set. IE came from a signaling NaN, which the conversion makes quiet, keeping its payload in the top bits of the single’s.

In compiled code

GCC 14 and Clang 23 at -O2 with -mf16c convert a _Float16 to float with VCVTPH2PS on the register; GCC first clears the rest of it with VPBLENDW, so the conversion sees zeros in the other elements. A loop widening an array of halves becomes the YMM form with a memory operand in Clang, as in the manual’s example (Example 15-33), while GCC converts one element at a time, inserting each half with VPINSRW. Adding two _Float16 values widens both, adds them with VADDSS and narrows the sum with VCVTPS2PH.

The EVEX forms (AVX-512F or AVX10.1) widen sixteen halves into a ZMM register, with masking and {sae}; VCVTPH2PSX of AVX512-FP16 adds broadcast. The instruction table of AMD’s Zen 5 guide gives the XMM form one macro-op with a latency of three cycles, and the YMM form from a register two macro-ops and four cycles.

In the optimization guide

What the optimization guide says about VCVTPH2PS, 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: The 256-bit forms that widen or insert data loaded from memory take two dependent micro-ops.

Zen and Zen+

Forms

Every encoding of VCVTPH2PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTPH2PS xmm, m64 VCVTPH2PS_XMMdq_MEMqVEX.128.66.0F38.W0 13 /rF16C
VCVTPH2PS xmm, xmm VCVTPH2PS_XMMdq_XMMqVEX.128.66.0F38.W0 13 /rF16C
VCVTPH2PS ymm, m128 VCVTPH2PS_YMMqq_MEMdqVEX.256.66.0F38.W0 13 /rF16C
VCVTPH2PS ymm, xmm VCVTPH2PS_YMMqq_XMMdqVEX.256.66.0F38.W0 13 /rF16C
VCVTPH2PS zmm {k}{z}, ymm, {sae} VCVTPH2PS_ZMMf32_MASKmskw_YMMf16_AVX512EVEX.512.66.0F38.W0 13 /rAVX10.1 or AVX512F
VCVTPH2PS zmm {k}{z}, m256 VCVTPH2PS_ZMMf32_MASKmskw_MEMf16_AVX512EVEX.512.66.0F38.W0 13 /rAVX10.1 or AVX512F
VCVTPH2PS xmm {k}{z}, xmm VCVTPH2PS_XMMf32_MASKmskw_XMMf16_AVX512EVEX.128.66.0F38.W0 13 /rAVX10.1 or AVX512F + AVX512VL
VCVTPH2PS xmm {k}{z}, m64 VCVTPH2PS_XMMf32_MASKmskw_MEMf16_AVX512EVEX.128.66.0F38.W0 13 /rAVX10.1 or AVX512F + AVX512VL
VCVTPH2PS ymm {k}{z}, xmm VCVTPH2PS_YMMf32_MASKmskw_XMMf16_AVX512EVEX.256.66.0F38.W0 13 /rAVX10.1 or AVX512F + AVX512VL
VCVTPH2PS ymm {k}{z}, m128 VCVTPH2PS_YMMf32_MASKmskw_MEMf16_AVX512EVEX.256.66.0F38.W0 13 /rAVX10.1 or AVX512F + AVX512VL

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, m64xmm, xmm
xmm {k}{z}, xmmno mask
ymm, m128ymm, xmm
ymm {k}{z}, xmmno mask
zmm {k}{z}, ymm, {sae}no mask, with {sae}zmm {k}{z}, ymm, {sae}with a mask, zeroingzmm {k}{z}, m256no maskzmm {k}{z}, m256with a mask, zeroingxmm {k}{z}, xmmwith a mask, zeroingxmm {k}{z}, m64no maskxmm {k}{z}, m64with a mask, zeroingymm {k}{z}, xmmwith a mask, zeroingymm {k}{z}, m128no maskymm {k}{z}, m128with a mask, zeroing
Sandy Bridge8 / 1p03 / 1p058 / 1p053 / 1p05
Haswell6 / 1p12 / 1p157 / 1p12 / 1p15
Broadwell6 / 1p12 / 1p156 / 1p12 / 1p15
Skylake9 / 0.5p015 / 1p01510 / 0.5p017 / 1p015
Skylake-SP, Ice Lake9 / 0.5p015 / 1p01510 / 0.5p017 / 1p0157 / 1p057 / 1p0511 / 0.5p0111 / 0.5p015 / 1p01510 / 0.5p0110 / 0.5p017 / 1p01511 / 0.5p0111 / 0.5p01
Alder Lake12 / 0.5p016 / 1p01512 / 0.5p018 / 1p015
Sapphire Rapids12 / 0.5p016 / 1p01512 / 0.5p018 / 1p0158 / 1p0511 / 1p0513 / 1p0516 / 1p059 / 1p01512 / 0.5p0114 / 0.5p0111 / 1p01512 / 0.5p0114 / 0.5p01
Lunar Lake12 / 0.5V0 V15 / 0.5V0 V1 V2 V311 / 2.33V0 V17 / 2V0 V1 V2 V3
Piledriver13 / 2FPCVT FPU08 / 2FPCVT FPSTO FPU013 / 2FPCVT FPU08 / 2FPCVT FPSTO FPU0
Zen, Zen 2100 / 0.25100 / 0.25100 / 0.25100 / 0.25
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP311 / 1FP2 FP34 / 1FP2 FP3
Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP311 / 1FP2 FP34 / 1FP2 FP34 / 21FP2 FP34 / 21FP2 FP311 / 2FP2 FP311 / 2FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP310 / 0.5FP2 FP34 / 12FP2 FP311 / 1FP2 FP311 / 1FP2 FP3
Jaguar8 / 1FPU13 / 1FPU1 STC8 / 2FPU13 / 2FPU1 STC
  1. Zen 4 model: AMD's spreadsheets give latency 6 for Zen 4 and Zen 5 (AMD 57647, row 1006; AMD 58455, row 60).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.67 for Zen 4 and Zen 5 (AMD 57647, row 1004; AMD 58455, row 58).

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.
VCVTPH2PS: 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 EVEX 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]:  # 1 without a write mask
        a = src2.f16[i]
        zmm1.f32[i] = to_f32_f16c(a)
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# {sae}: no exception flags
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 15 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
VCVTPH2PS xmm, xmm/m64 VCVTPH2PS ymm, xmm/m128
xmm, ymmexplicitwrite
xmm/m64/128explicitread
VCVTPH2PS xmm {k}{z}, xmm/m64 VCVTPH2PS ymm {k}{z}, xmm/m128 VCVTPH2PS zmm {k}{z}, ymm/m256, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m64, xmm/m128, ymm/m256explicitread

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-11
EVEX forms
AVX512-E11

Attributes

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

All forms
follows MXCSR
EVEX forms
write masking
EVEX memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTPH2PS, 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_cvtph_ps __m128 _mm_cvtph_ps(__m128i __a)

VCVTPH2PS xmm, xmm VEX.128 -mf16c

_mm_mask_cvtph_ps __m128 _mm_mask_cvtph_ps(__m128 __W, __mmask8 __U, __m128i __A)

VCVTPH2PS xmm {k}, xmm EVEX.128 -mavx512vl

_mm_maskz_cvtph_ps __m128 _mm_maskz_cvtph_ps(__mmask8 __U, __m128i __A)

VCVTPH2PS xmm {k}{z}, xmm EVEX.128 -mavx512vl

_mm256_cvtph_ps __m256 _mm256_cvtph_ps(__m128i __a)

VCVTPH2PS ymm, xmm VEX.256 -mf16c

_mm256_mask_cvtph_ps __m256 _mm256_mask_cvtph_ps(__m256 __W, __mmask8 __U, __m128i __A)

VCVTPH2PS ymm {k}, xmm EVEX.256 -mavx512vl

_mm256_maskz_cvtph_ps __m256 _mm256_maskz_cvtph_ps(__mmask8 __U, __m128i __A)

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

_mm512_cvt_roundph_ps __m512 _mm512_cvt_roundph_ps(__m256i A, const int R)

VCVTPH2PS zmm, ymm, {sae} EVEX.512 -mavx512f

_mm512_cvtph_ps __m512 _mm512_cvtph_ps(__m256i __A)

VCVTPH2PS zmm, ymm EVEX.512 -mavx512f

_mm512_mask_cvt_roundph_ps __m512 _mm512_mask_cvt_roundph_ps(__m512 W, __mmask16 U, __m256i A, const int R)

VCVTPH2PS zmm {k}, ymm, {sae} EVEX.512 -mavx512f

_mm512_mask_cvtph_ps __m512 _mm512_mask_cvtph_ps(__m512 __W, __mmask16 __U, __m256i __A)

VCVTPH2PS zmm {k}, ymm EVEX.512 -mavx512f

_mm512_maskz_cvt_roundph_ps __m512 _mm512_maskz_cvt_roundph_ps(__mmask16 U, __m256i A, const int R)

VCVTPH2PS zmm {k}{z}, ymm, {sae} EVEX.512 -mavx512f

_mm512_maskz_cvtph_ps __m512 _mm512_maskz_cvtph_ps(__mmask16 __U, __m256i __A)

VCVTPH2PS zmm {k}{z}, ymm EVEX.512 -mavx512f

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
F16C

F16C
CPUID.01H:ECX[29] F16C

Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6

Note: XED gives Bulldozer F16C; GCC enables it from -march=bdver2 (Piledriver) on.

AVX512F_512

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

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512F_128

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

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512F_256
Same as AVX512F_128Same as AVX512F_128

More F16C 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-54 (VCVTPH2PS/VCVTPH2PSX)
  6. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  7. AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit, 256-Bit, and 512-Bit Media Instructions (26568, rev. 3.27, July 2026)
  8. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
  9. 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.