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

VCVTUQQ2PD converts each unsigned quadword of an XMM, YMM or ZMM register, or of memory, to a double: the vector form of C’s conversion from uint64_t to double. It is the unsigned partner of VCVTQQ2PD, whose page covers the rounding, and came with it in AVX512DQ; VCVTUQQ2PS converts to singles. The difference from the signed form is the top bit: 8000000000000000h is 2^63 here, and the largest input is 2^64 - 1. A double holds every integer up to 2^53 exactly; a larger one is rounded as MXCSR.RC says or, in the 512-bit register form, as the {er} operand says, and an inexact result sets PE, the only exception it can raise.

Recorded on Zen 5

  • Up. With MXCSR rounding up, 2^63 - 513 gave 2^63 and set PE, while 2^32 - 1 converted exactly.
  • Down. 8000000000000001h, 2^63 + 1, gave 2^63 and set PE.
  • Toward zero. FFFFFFFFFFFFFFFEh gave 2^64 - 2048, the largest double below 2^64, and 2^63 - 513 gave 2^63 - 1024.
  • An override. Under {rn-sae}, 2^64 - 1 gave 2^64 and 2^63 - 1 gave 2^63, while 1 and 2^24 + 3 converted exactly; MXCSR stayed unchanged.

In compiled code

At -O2 with -march=x86-64-v4, both compilers vectorize d[i] = (double)u[i] over uint64_t with VCVTUQQ2PD straight from memory, GCC 14 on ZMM registers and Clang 23 on YMM registers. A single conversion is VCVTUSI2SD. The intrinsic is _mm512_cvtepu64_pd; the SDM’s list for this entry names it _mm512_cvtepu64_ps, with a __m512d result.

AMD’s Zen 5 latency spreadsheet gives every width one macro-op on pipe FP2 or FP3 and 3 cycles.

Forms

Every encoding of VCVTUQQ2PD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTUQQ2PD xmm {k}{z}, xmm VCVTUQQ2PD_XMMf64_MASKmskw_XMMu64_AVX512EVEX.128.F3.0F.W1 7A /rAVX10.1 or AVX512DQ + AVX512VL
VCVTUQQ2PD xmm {k}{z}, m128/m64bcst VCVTUQQ2PD_XMMf64_MASKmskw_MEMu64_AVX512EVEX.128.F3.0F.W1 7A /rAVX10.1 or AVX512DQ + AVX512VL
VCVTUQQ2PD ymm {k}{z}, ymm VCVTUQQ2PD_YMMf64_MASKmskw_YMMu64_AVX512EVEX.256.F3.0F.W1 7A /rAVX10.1 or AVX512DQ + AVX512VL
VCVTUQQ2PD ymm {k}{z}, m256/m64bcst VCVTUQQ2PD_YMMf64_MASKmskw_MEMu64_AVX512EVEX.256.F3.0F.W1 7A /rAVX10.1 or AVX512DQ + AVX512VL
VCVTUQQ2PD zmm {k}{z}, zmm, {er} VCVTUQQ2PD_ZMMf64_MASKmskw_ZMMu64_AVX512EVEX.512.F3.0F.W1 7A /rAVX10.1 or AVX512DQ
VCVTUQQ2PD zmm {k}{z}, m512/m64bcst VCVTUQQ2PD_ZMMf64_MASKmskw_MEMu64_AVX512EVEX.512.F3.0F.W1 7A /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/m64bcstymm {k}{z}, ymmymm {k}{z}, m256/m64bcstzmm {k}{z}, zmm, {er}zmm {k}{z}, m512/m64bcst
Skylake-SP, Ice Lake4 / 0.5p0110 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p0511 / 0.5p01
Sapphire Rapids4 / 0.5p0111 / 0.5p014 / 0.5p0112 / 0.5p014 / 1p012 / 1p0
Zen 43 / 0.5FP2 FP310 / 0.5FP2 FP33 / 1FP2 FP310 / 1FP2 FP34 / 2FP2 FP311 / 2FP2 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.

Element-wise: each quadword of the result comes from the quadword in the same place in each source.
VCVTUQQ2PD: element by elementResult quadword i comes from quadword i of xmm2. Result quadwords 1 to 0: r1, r0.01xmm2or m128a11k1r0r1xmm1

Every quadword works alike: 2, 4 and 8 quadwords in the xmm, ymm and zmm forms. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m64bcst, one quadword from memory stands for every element of the last source.

Result quadword i comes from quadword i of xmm2. Result quadwords 1 to 0: r1, r0.

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.q[i])
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[i] keeps its value
# m64bcst: src2.q[i] is the m64 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# zmm1 is zeroed from bit VL 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
VCVTUQQ2PD xmm {k}{z}, xmm/m128/m64bcst VCVTUQQ2PD ymm {k}{z}, ymm/m256/m64bcst VCVTUQQ2PD zmm {k}{z}, zmm/m512/m64bcst, {er}
xmm, ymm, zmmexplicitwrite (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 VCVTUQQ2PD, 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_cvtepu64_pd __m128d _mm_cvtepu64_pd(__m128i __A)

VCVTUQQ2PD xmm, xmm EVEX.128 -mavx512vl -mavx512dq

_mm_mask_cvtepu64_pd __m128d _mm_mask_cvtepu64_pd(__m128d __W, __mmask8 __U, __m128i __A)

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

_mm_maskz_cvtepu64_pd __m128d _mm_maskz_cvtepu64_pd(__mmask8 __U, __m128i __A)

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

_mm256_cvtepu64_pd __m256d _mm256_cvtepu64_pd(__m256i __A)

VCVTUQQ2PD ymm, ymm EVEX.256 -mavx512vl -mavx512dq

_mm256_mask_cvtepu64_pd __m256d _mm256_mask_cvtepu64_pd(__m256d __W, __mmask8 __U, __m256i __A)

VCVTUQQ2PD ymm {k}, ymm EVEX.256 -mavx512vl -mavx512dq

_mm256_maskz_cvtepu64_pd __m256d _mm256_maskz_cvtepu64_pd(__mmask8 __U, __m256i __A)

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

_mm512_cvt_roundepu64_pd __m512d _mm512_cvt_roundepu64_pd(__m512i A, const int R)

VCVTUQQ2PD zmm, zmm, {er} EVEX.512 -mavx512dq

_mm512_cvtepu64_pd __m512d _mm512_cvtepu64_pd(__m512i __A)

VCVTUQQ2PD zmm, zmm EVEX.512 -mavx512dq

_mm512_mask_cvt_roundepu64_pd __m512d _mm512_mask_cvt_roundepu64_pd(__m512d W, __mmask8 U, __m512i A, const int R)

VCVTUQQ2PD zmm {k}, zmm, {er} EVEX.512 -mavx512dq

_mm512_mask_cvtepu64_pd __m512d _mm512_mask_cvtepu64_pd(__m512d __W, __mmask8 __U, __m512i __A)

VCVTUQQ2PD zmm {k}, zmm EVEX.512 -mavx512dq

_mm512_maskz_cvt_roundepu64_pd __m512d _mm512_maskz_cvt_roundepu64_pd(__mmask8 U, __m512i A, const int R)

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

_mm512_maskz_cvtepu64_pd __m512d _mm512_maskz_cvtepu64_pd(__mmask8 __U, __m512i __A)

VCVTUQQ2PD zmm {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-138 (VCVTUQQ2PD)
  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.