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

VCVTQQ2PS converts signed quadwords to singles, the vector form of C’s conversion from long to float. The result is half as wide as the source: 8 quadwords of a ZMM register become 8 singles in a YMM register, 4 from a YMM register fill an XMM register, and 2 from an XMM register fill its low 64 bits; everything above is cleared. It came with AVX512DQ, as VCVTQQ2PD did, whose page covers the conversion to doubles; VCVTUQQ2PS converts unsigned quadwords, and CVTDQ2PS doublewords.

Recorded on Zen 5

  • 24 bits of significand. Rounding down, 2^24 + 1 became 2^24 and set PE, while -1 and -2^63 converted exactly.
  • Near 2^63. With {rz-sae} on the 512-bit register form, 2^63 - 1024 and 2^63 - 513 both became 2^63 - 2^39, the largest single below 2^63, -2^63 + 1 became -(2^63 - 2^39), and 2^31 - 64 became 2^31 - 128. MXCSR had PE unmasked, yet nothing faulted and PE stayed clear: the {sae} part suppresses the flags.
  • Nothing selected. vcvtqq2ps xmm5{k1}, ymmword ptr [mem], with the low four bits of K1 clear, kept the four singles of XMM5 and cleared the register above bit 127.

In compiled code

At -O2 with -march=x86-64-v4, GCC 14 and Clang 23 compile f[i] = (float)q[i] over int64_t and float arrays to VCVTQQ2PS with the source in memory. GCC converts two ZMM loads to YMM halves and joins them with VINSERTF32X8 for one ZMM store; Clang converts YMM loads to XMM registers and stores those. For a loop of unknown length Clang still uses VCVTQQ2PS, while GCC converts one element at a time with VCVTSI2SS. With -march=x86-64-v3, which has no AVX512DQ, both convert one element at a time, Clang gathering four results with VINSERTPS. _mm512_cvt_roundepi64_ps with _MM_FROUND_TO_ZERO is the {rz-sae} form.

AMD’s Zen 5 latency spreadsheet gives VCVTQQ2PS one macro-op and 3 cycles from an XMM source, and two macro-ops with 6 cycles from a YMM source and 7 from a ZMM source.

Forms

Every encoding of VCVTQQ2PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTQQ2PS xmm {k}{z}, xmm VCVTQQ2PS_XMMf32_MASKmskw_XMMu64_AVX512_VL128EVEX.128.NP.0F.W1 5B /rAVX10.1 or AVX512DQ + AVX512VL
VCVTQQ2PS xmm {k}{z}, m128/m64bcst VCVTQQ2PS_XMMf32_MASKmskw_MEMu64_AVX512_VL128EVEX.128.NP.0F.W1 5B /rAVX10.1 or AVX512DQ + AVX512VL
VCVTQQ2PS xmm {k}{z}, ymm VCVTQQ2PS_XMMf32_MASKmskw_YMMu64_AVX512_VL256EVEX.256.NP.0F.W1 5B /rAVX10.1 or AVX512DQ + AVX512VL
VCVTQQ2PS xmm {k}{z}, m256/m64bcst VCVTQQ2PS_XMMf32_MASKmskw_MEMu64_AVX512_VL256EVEX.256.NP.0F.W1 5B /rAVX10.1 or AVX512DQ + AVX512VL
VCVTQQ2PS ymm {k}{z}, zmm, {er} VCVTQQ2PS_YMMf32_MASKmskw_ZMMu64_AVX512_VL512EVEX.512.NP.0F.W1 5B /rAVX10.1 or AVX512DQ
VCVTQQ2PS ymm {k}{z}, m512/m64bcst VCVTQQ2PS_YMMf32_MASKmskw_MEMu64_AVX512_VL512EVEX.512.NP.0F.W1 5B /rAVX10.1 or AVX512DQ

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}, xmmxmm {k}{z}, m128/m64bcstxmm {k}{z}, ymmxmm {k}{z}, m256/m64bcstymm {k}{z}, zmm, {er}no maskymm {k}{z}, zmm, {er}with a mask, zeroing, with {er}ymm {k}{z}, m512/m64bcst
Skylake-SP, Ice Lake5 / 1p01510 / 0.5p017 / 1p01511 / 0.5p017 / 1p054 / 0.5p0514 / 1p015
Sapphire Rapids5 / 1p01512 / 1p0157 / 1p01515 / 1p0157 / 1p057 / 1p0515 / 1p05
Zen 43 / 0.5FP2 FP310 / 0.5FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP33 / 1FP2 FP33 / 1FP2 FP310 / 1FP2 FP3

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 single, in the same order, at the low end of the result.
VCVTQQ2PS: each element narrowedResult singles 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.01234567zmm2or m512a11111110k1a0a1a2a3a4a5a7ymm1

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 singles 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]:
        ymm1.f32[i] = to_f32(src2.sq[i])
    elif zeroing:
        ymm1.f32[i] = 0
    # else: ymm1.f32[i] keeps its value
for i in range(VL // 64, 4):
    ymm1.d[i] = 0
# m64bcst: src2.q[i] is the m64 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

Run on AMD Zen 5 (EPYC 9645): 9 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
VCVTQQ2PS xmm {k}{z}, xmm/m128/m64bcst VCVTQQ2PS xmm {k}{z}, ymm/m256/m64bcst VCVTQQ2PS ymm {k}{z}, zmm/m512/m64bcst, {er}
xmm, ymmexplicitwrite (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 VCVTQQ2PS, 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_ps __m128 _mm_cvtepi64_ps(__m128i __A)

VCVTQQ2PS xmm, xmm EVEX.128 -mavx512vl -mavx512dq

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

VCVTQQ2PS xmm {k}, xmm EVEX.128 -mavx512vl -mavx512dq

_mm_maskz_cvtepi64_ps __m128 _mm_maskz_cvtepi64_ps(__mmask8 __U, __m128i __A)

VCVTQQ2PS xmm {k}{z}, xmm EVEX.128 -mavx512vl -mavx512dq

_mm256_cvtepi64_ps __m128 _mm256_cvtepi64_ps(__m256i __A)

VCVTQQ2PS xmm, ymm EVEX.256 -mavx512vl -mavx512dq

_mm256_mask_cvtepi64_ps __m128 _mm256_mask_cvtepi64_ps(__m128 __W, __mmask8 __U, __m256i __A)

VCVTQQ2PS xmm {k}, ymm EVEX.256 -mavx512vl -mavx512dq

_mm256_maskz_cvtepi64_ps __m128 _mm256_maskz_cvtepi64_ps(__mmask8 __U, __m256i __A)

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

_mm512_cvt_roundepi64_ps __m256 _mm512_cvt_roundepi64_ps(__m512i A, const int R)

VCVTQQ2PS ymm, zmm, {er} EVEX.512 -mavx512dq

_mm512_cvtepi64_ps __m256 _mm512_cvtepi64_ps(__m512i __A)

VCVTQQ2PS ymm, zmm EVEX.512 -mavx512dq

_mm512_mask_cvt_roundepi64_ps __m256 _mm512_mask_cvt_roundepi64_ps(__m256 W, __mmask8 U, __m512i A, const int R)

VCVTQQ2PS ymm {k}, zmm, {er} EVEX.512 -mavx512dq

_mm512_mask_cvtepi64_ps __m256 _mm512_mask_cvtepi64_ps(__m256 __W, __mmask8 __U, __m512i __A)

VCVTQQ2PS ymm {k}, zmm EVEX.512 -mavx512dq

_mm512_maskz_cvt_roundepi64_ps __m256 _mm512_maskz_cvt_roundepi64_ps(__mmask8 U, __m512i A, const int R)

VCVTQQ2PS ymm {k}{z}, zmm, {er} EVEX.512 -mavx512dq

_mm512_maskz_cvtepi64_ps __m256 _mm512_maskz_cvtepi64_ps(__mmask8 __U, __m512i __A)

VCVTQQ2PS ymm {k}{z}, zmm EVEX.512 -mavx512dq

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
AVX512DQ_128

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

or

AVX512DQ + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ
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
AVX512DQ_256
Same as AVX512DQ_128Same as AVX512DQ_128
AVX512DQ_512

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

or

AVX512DQ
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ

Same as AVX512DQ_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-85 (VCVTQQ2PS)
  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.