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

VCVTPH2PD widens half-precision values to doubles: two from the low 32 bits of the source into an xmm register, four from 64 bits into a ymm register, eight from 128 bits into a zmm register. Every half, denormals included, is exactly a double, so nothing is rounded and the result never depends on MXCSR.RC; Intel’s optimization manual notes that a denormal half becomes a normal value in the wider format (Section 18.5.7).

It came with AVX512-FP16 (CPUID leaf 7, EDX bit 23, with AVX512VL for the xmm and ymm forms) and is part of AVX10.1; VADDPH covers that extension. F16C, the older extension, has only VCVTPH2PS and its way back: before AVX512-FP16, a half reached double precision in two steps, through a single. The opcode is that of CVTPS2PD, 5Ah without a prefix, in EVEX map 5. The source is a quarter of the destination’s width: the zmm form reads an xmm register or 16 bytes of memory, the xmm form only 4 bytes, and one half from memory can be broadcast to every element.

Flags that differ from VCVTPH2PS

Intel’s manual lists invalid and denormal as the exceptions VCVTPH2PD can report, as it does for VCVTPH2PSX, the AVX512-FP16 conversion to singles. For VCVTPH2PS, the F16C and AVX512F one, it states the opposite for denormals: no denormal exception, and MXCSR.DAZ ignored. A program that unmasks the denormal exception cannot count on the newer conversions behaving like VCVTPH2PS there; a signaling NaN sets the invalid flag in all of them. The zmm register form takes {sae}, which suppresses both flags and any #XM.

In compiled code

With -march=sapphirerapids, Clang 23 at -O2 widens an array of _Float16 into an array of double with VCVTPH2PD from memory into ymm registers. GCC 14 at -O2 converts one element at a time with VCVTSH2SD when the count is known only at run time or leaves a remainder, as 1,001 does; for a constant count that fills whole vectors, such as 1,024, it vectorizes in two steps, VCVTPH2PSX and then VCVTPS2PD, over global arrays and through pointer parameters alike. At -O3 it takes those two steps for every count and finishes any remainder with VCVTSH2SD. Without AVX512-FP16, as with -march=znver5, Clang uses VCVTPH2PS and VCVTPS2PD, and GCC calls the library routine __extendhfdf2 for each element. Both routes give the same doubles, since the single in between is exact.

Forms

Every encoding of VCVTPH2PD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTPH2PD xmm {k}{z}, xmm VCVTPH2PD_XMMf64_MASKmskw_XMMf16_AVX512EVEX.128.NP.MAP5.W0 5A /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPH2PD xmm {k}{z}, m32/m16bcst VCVTPH2PD_XMMf64_MASKmskw_MEMf16_AVX512EVEX.128.NP.MAP5.W0 5A /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPH2PD ymm {k}{z}, xmm VCVTPH2PD_YMMf64_MASKmskw_XMMf16_AVX512EVEX.256.NP.MAP5.W0 5A /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPH2PD ymm {k}{z}, m64/m16bcst VCVTPH2PD_YMMf64_MASKmskw_MEMf16_AVX512EVEX.256.NP.MAP5.W0 5A /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPH2PD zmm {k}{z}, xmm, {sae} VCVTPH2PD_ZMMf64_MASKmskw_XMMf16_AVX512EVEX.512.NP.MAP5.W0 5A /rAVX10.1 or AVX512_FP16
VCVTPH2PD zmm {k}{z}, m128/m16bcst VCVTPH2PD_ZMMf64_MASKmskw_MEMf16_AVX512EVEX.512.NP.MAP5.W0 5A /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}, m32/m16bcstno mask, broadcastxmm {k}{z}, m32/m16bcstwith a mask, zeroingymm {k}{z}, xmmno maskymm {k}{z}, xmmwith a mask, zeroingymm {k}{z}, m64/m16bcstno mask, broadcastymm {k}{z}, m64/m16bcstwith a mask, zeroingzmm {k}{z}, xmm, {sae}no mask, with {sae}zmm {k}{z}, xmm, {sae}with a mask, zeroingzmm {k}{z}, m128/m16bcstno mask, broadcastzmm {k}{z}, m128/m16bcstwith a mask, zeroing
Sapphire Rapids16 / 2p015619 / 2p015623 / 2p015626 / 2p015615 / 2p01518 / 2p01522 / 2p01525 / 2p01515 / 2p0518 / 2p0523 / 2p05626 / 2p056

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 double, converted, in the same order.
VCVTPH2PD: each element widenedResult doubles 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.01234567xmm2or m128a11111110k1a0a1a2a3a4a5a7zmm1

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

Result doubles 7 to 0: a7, unchanged (bit 6 of k1 is 0), 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 // 64):
    if k1[i]:
        zmm1.f64[i] = to_f64(src2.f16[i])
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[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
VCVTPH2PD xmm {k}{z}, xmm/m32/m16bcst VCVTPH2PD ymm {k}{z}, xmm/m64/m16bcst VCVTPH2PD zmm {k}{z}, xmm/m128/m16bcst, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m32/64/128/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 Quarter); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTPH2PD, 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_pd __m128d _mm_cvtph_pd(__m128h __A)

VCVTPH2PD xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_mask_cvtph_pd __m128d _mm_mask_cvtph_pd(__m128d __W, __mmask8 __U, __m128h __A)

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

_mm_maskz_cvtph_pd __m128d _mm_maskz_cvtph_pd(__mmask8 __U, __m128h __A)

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

_mm256_cvtph_pd __m256d _mm256_cvtph_pd(__m128h __A)

VCVTPH2PD ymm, xmm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_mask_cvtph_pd __m256d _mm256_mask_cvtph_pd(__m256d __W, __mmask8 __U, __m128h __A)

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

_mm256_maskz_cvtph_pd __m256d _mm256_maskz_cvtph_pd(__mmask8 __U, __m128h __A)

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

_mm512_cvt_roundph_pd __m512d _mm512_cvt_roundph_pd(__m128h A, const int R)

VCVTPH2PD zmm, xmm, {sae} EVEX.512 -mavx512fp16

_mm512_cvtph_pd __m512d _mm512_cvtph_pd(__m128h __A)

VCVTPH2PD zmm, xmm EVEX.512 -mavx512fp16

_mm512_mask_cvt_roundph_pd __m512d _mm512_mask_cvt_roundph_pd(__m512d W, __mmask8 U, __m128h A, const int R)

VCVTPH2PD zmm {k}, xmm, {sae} EVEX.512 -mavx512fp16

_mm512_mask_cvtph_pd __m512d _mm512_mask_cvtph_pd(__m512d __W, __mmask8 __U, __m128h __A)

VCVTPH2PD zmm {k}, xmm EVEX.512 -mavx512fp16

_mm512_maskz_cvt_roundph_pd __m512d _mm512_maskz_cvt_roundph_pd(__mmask8 U, __m128h A, const int R)

VCVTPH2PD zmm {k}{z}, xmm, {sae} EVEX.512 -mavx512fp16

_mm512_maskz_cvtph_pd __m512d _mm512_maskz_cvtph_pd(__mmask8 __U, __m128h __A)

VCVTPH2PD zmm {k}{z}, xmm 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-52 (VCVTPH2PD)
  7. 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.