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

VCVTQQ2PH converts signed quadwords to half precision, the vector form of C’s conversion from long to _Float16. The result is a quarter as wide as the source: 8 quadwords of a ZMM register become 8 halves filling an XMM register, 4 from a YMM register fill its low 64 bits and 2 from an XMM register its low 32 bits, with everything above cleared. The opcode is 5Bh without a prefix in EVEX map 5 with W1, which tells it apart from VCVTDQ2PH (W0), as W does for VCVTQQ2PS and CVTDQ2PS in the 0F map. VCVTUQQ2PH converts unsigned quadwords.

Sixty-four bits into sixteen

A half is exact for integers up to 2048 and has no finite value past 65504, so nearly all of the quadword range overflows: in round to nearest, from 65520 up the result is infinity, and toward zero it is 65504; Intel’s entry lists overflow and precision. The rounding mode comes from MXCSR.RC, or from {er} on the 512-bit register form, and a quadword broadcast from memory is allowed. The VCVTDQ2PH page works through the rounding near the top of the range.

In our builds

At -O2 with -march=x86-64-v4 -mavx512fp16, Clang 23 converts an int64_t array into a _Float16 array with VCVTQQ2PH from YMM loads to XMM results, joining four of them with VINSERTF128 and VUNPCKLPD for a 32-byte store. GCC 14 does not use it, at -O2 or -O3: it converts each element with VCVTSI2SH straight from memory and stores the half with VMOVW. Without AVX512-FP16, at -march=x86-64-v3, Clang converts each element to a single with VCVTSI2SS and narrows it with VCVTPS2PH, the same result, since every integer a half can hold is exact as a single and the rest overflow either way; GCC loads each quadword with the x87 FILD and calls the library’s __truncxfhf2. AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VCVTQQ2PH.

Forms

Every encoding of VCVTQQ2PH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTQQ2PH xmm {k}{z}, xmm VCVTQQ2PH_XMMf16_MASKmskw_XMMu64_AVX512EVEX.128.NP.MAP5.W1 5B /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTQQ2PH xmm {k}{z}, m128/m64bcst VCVTQQ2PH_XMMf16_MASKmskw_MEMu64_AVX512_VL128EVEX.128.NP.MAP5.W1 5B /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTQQ2PH xmm {k}{z}, ymm VCVTQQ2PH_XMMf16_MASKmskw_YMMu64_AVX512EVEX.256.NP.MAP5.W1 5B /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTQQ2PH xmm {k}{z}, m256/m64bcst VCVTQQ2PH_XMMf16_MASKmskw_MEMu64_AVX512_VL256EVEX.256.NP.MAP5.W1 5B /rAVX10.1 or AVX512_FP16 + AVX512VL
VCVTQQ2PH xmm {k}{z}, zmm, {er} VCVTQQ2PH_XMMf16_MASKmskw_ZMMu64_AVX512EVEX.512.NP.MAP5.W1 5B /rAVX10.1 or AVX512_FP16
VCVTQQ2PH xmm {k}{z}, m512/m64bcst VCVTQQ2PH_XMMf16_MASKmskw_MEMu64_AVX512_VL512EVEX.512.NP.MAP5.W1 5B /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, zeroing
xmm {k}{z}, ymmno mask
xmm {k}{z}, m128/m64bcstno mask, broadcastxmm {k}{z}, m128/m64bcstwith a mask, zeroingxmm {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 Rapids8 / 1.33p01510 / 1.33p01515 / 1.33p01517 / 1.33p01512 / 1.33p01518 / 1.33p01520 / 1.33p01510 / 2p0512 / 2p0518 / 2p0520 / 2p05

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 quadword becomes a half, in the same order, at the low end of the result.
VCVTQQ2PH: 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 quadwords. 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.sq[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.q[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
VCVTQQ2PH xmm {k}{z}, xmm/m128/m64bcst VCVTQQ2PH xmm {k}{z}, ymm/m256/m64bcst VCVTQQ2PH 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 VCVTQQ2PH, 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_cvtepi64_ph __m128h _mm_cvtepi64_ph(__m128i __A)

VCVTQQ2PH xmm, xmm EVEX.128 -mavx512fp16 -mavx512vl

_mm_mask_cvtepi64_ph __m128h _mm_mask_cvtepi64_ph(__m128h __W, __mmask8 __U, __m128i __A)

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

_mm_maskz_cvtepi64_ph __m128h _mm_maskz_cvtepi64_ph(__mmask8 __U, __m128i __A)

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

_mm256_cvtepi64_ph __m128h _mm256_cvtepi64_ph(__m256i __A)

VCVTQQ2PH xmm, ymm EVEX.256 -mavx512fp16 -mavx512vl

_mm256_mask_cvtepi64_ph __m128h _mm256_mask_cvtepi64_ph(__m128h __W, __mmask8 __U, __m256i __A)

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

_mm256_maskz_cvtepi64_ph __m128h _mm256_maskz_cvtepi64_ph(__mmask8 __U, __m256i __A)

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

_mm512_cvt_roundepi64_ph __m128h _mm512_cvt_roundepi64_ph(__m512i A, const int R)

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

_mm512_cvtepi64_ph __m128h _mm512_cvtepi64_ph(__m512i __A)

VCVTQQ2PH xmm, zmm EVEX.512 -mavx512fp16

_mm512_mask_cvt_roundepi64_ph __m128h _mm512_mask_cvt_roundepi64_ph(__m128h W, __mmask8 U, __m512i A, const int R)

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

_mm512_mask_cvtepi64_ph __m128h _mm512_mask_cvtepi64_ph(__m128h __W, __mmask8 __U, __m512i __A)

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

_mm512_maskz_cvt_roundepi64_ph __m128h _mm512_maskz_cvt_roundepi64_ph(__mmask8 U, __m512i A, const int R)

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

_mm512_maskz_cvtepi64_ph __m128h _mm512_maskz_cvtepi64_ph(__mmask8 __U, __m512i __A)

VCVTQQ2PH 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-83 (VCVTQQ2PH)
  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.