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

VCVTPD2PH narrows doubles to half precision: 2, 4 or 8 of them from an XMM, YMM or ZMM register or memory into the low 32, 64 or 128 bits of an XMM register, with the rest cleared. It rounds by MXCSR.RC or by an {er} mode on the 512-bit register form, takes a double broadcast from memory and a write mask, and can overflow to infinity past 65504 or underflow to a denormal or zero. The opcode is that of VCVTPD2PS, 5Ah with the 66 prefix, in EVEX map 5 with W1; VCVTPH2PD is the way back and VCVTSD2SH the scalar form.

One rounding, not two

Intel’s entry says that DAZ applies to the double inputs and that the half results are never flushed to zero, as for VCVTPS2PHX. Narrowing in one step matters, because going through a single rounds twice. Take 1 + 2^-11 + 2^-40, just above halfway between the halves 1 and 1 + 2^-10, so that the correctly rounded half is 1 + 2^-10, which VCVTPD2PH gives. As a single it first becomes 1 + 2^-11, since 2^-40 is far below a single’s spacing of 2^-23 at 1; that single is exactly halfway between the two halves, and round to nearest even then gives 1.

In our builds

GCC 14.2.0 and Clang 23.1.2, at -O2 with -march=x86-64-v4 -mavx512fp16, compile h[i] = d[i] over global double and _Float16 arrays of 1024 elements differently. Clang converts with VCVTPD2PH from YMM loads, joining the XMM results with VINSERTF128 and VUNPCKLPD. GCC goes through singles, VCVTPD2PS and then VCVTPS2PHX, at -O2 and -O3 and also with -march=sapphirerapids, so for the value above its loop stores 1 where the correctly rounded result is 1 + 2^-10. The count decides, not how the arrays are passed: pointer parameters give the same two steps for 1024 elements, while at -O2 a count known only at run time, or one that leaves a remainder such as 1,001, keeps GCC’s loop scalar with VCVTSD2SH, rounding once. At -O3 GCC takes the two steps for any count and converts the remainder with VCVTSD2SH, the instruction it also uses for a single double. _mm512_cvtpd_ph gives VCVTPD2PH in both compilers, and Clang folds _mm512_set1_pd(*p) into a {1to8} broadcast where GCC uses VBROADCASTSD. AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VCVTPD2PH.

Forms

Every encoding of VCVTPD2PH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTPD2PH xmm {k}{z}, xmm VCVTPD2PH_XMMf16_MASKmskw_XMMf64_AVX512EVEX.128.66.MAP5.W1 5A /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPD2PH xmm {k}{z}, m128/m64bcst VCVTPD2PH_XMMf16_MASKmskw_MEMf64_AVX512_VL128EVEX.128.66.MAP5.W1 5A /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPD2PH xmm {k}{z}, ymm VCVTPD2PH_XMMf16_MASKmskw_YMMf64_AVX512EVEX.256.66.MAP5.W1 5A /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPD2PH xmm {k}{z}, m256/m64bcst VCVTPD2PH_XMMf16_MASKmskw_MEMf64_AVX512_VL256EVEX.256.66.MAP5.W1 5A /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTPD2PH xmm {k}{z}, zmm, {er} VCVTPD2PH_XMMf16_MASKmskw_ZMMf64_AVX512EVEX.512.66.MAP5.W1 5A /rAVX10.1 or AVX512_FP16
VCVTPD2PH xmm {k}{z}, m512/m64bcst VCVTPD2PH_XMMf16_MASKmskw_MEMf64_AVX512_VL512EVEX.512.66.MAP5.W1 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}, m128/m64bcstno mask, broadcastxmm {k}{z}, m128/m64bcstwith a mask, zeroingxmm {k}{z}, ymmno maskxmm {k}{z}, ymmwith a mask, zeroingxmm {k}{z}, m256/m64bcstno mask, broadcastxmm {k}{z}, m256/m64bcstwith a mask, zeroingxmm {k}{z}, zmm, {er}no mask, with {er}xmm {k}{z}, zmm, {er}with a mask, zeroingxmm {k}{z}, m512/m64bcstno mask, broadcastxmm {k}{z}, m512/m64bcstwith a mask, zeroing
Sapphire Rapids12 / 2p01515 / 2p01519 / 2p015622 / 2p015613 / 2p01516 / 2p01521 / 2p015624 / 2p015615 / 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.

Narrow: each double becomes a half, in the same order, at the low end of the result.
VCVTPD2PH: each element narrowedResult halves 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.01234567zmm2or m512a11111110k1a0a1a2a3a4a5a7xmm1

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

Result halves 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]:
        xmm1.f16[i] = to_f16(src2.f64[i])
    elif zeroing:
        xmm1.f16[i] = 0
    # else: xmm1.f16[i] keeps its value
for i in range(VL // 64, 8):
    xmm1.w[i] = 0
# m64bcst: src2.f64[i] is the m64 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# xmm1 is zeroed from bit 128 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
VCVTPD2PH xmm {k}{z}, xmm/m128/m64bcst VCVTPD2PH xmm {k}{z}, ymm/m256/m64bcst VCVTPD2PH xmm {k}{z}, zmm/m512/m64bcst, {er}
xmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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 VCVTPD2PH, 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_cvtpd_ph __m128h _mm_cvtpd_ph(__m128d __A)

VCVTPD2PH xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

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

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

_mm_maskz_cvtpd_ph __m128h _mm_maskz_cvtpd_ph(__mmask8 __U, __m128d __A)

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

_mm256_cvtpd_ph __m128h _mm256_cvtpd_ph(__m256d __A)

VCVTPD2PH xmm, ymm EVEX.256 -mavx512fp16 -mavx512vl

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

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

_mm256_maskz_cvtpd_ph __m128h _mm256_maskz_cvtpd_ph(__mmask8 __U, __m256d __A)

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

_mm512_cvt_roundpd_ph __m128h _mm512_cvt_roundpd_ph(__m512d A, const int R)

VCVTPD2PH xmm, zmm, {er} EVEX.512 -mavx512fp16

_mm512_cvtpd_ph __m128h _mm512_cvtpd_ph(__m512d __A)

VCVTPD2PH xmm, zmm EVEX.512 -mavx512fp16

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

VCVTPD2PH xmm {k}, zmm, {er} EVEX.512 -mavx512fp16

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

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

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

VCVTPD2PH xmm {k}{z}, zmm, {er} EVEX.512 -mavx512fp16

_mm512_maskz_cvtpd_ph __m128h _mm512_maskz_cvtpd_ph(__mmask8 __U, __m512d __A)

VCVTPD2PH xmm {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-40 (VCVTPD2PH)
  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.