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

VCVTTPD2UQQ converts each double of an XMM, YMM or ZMM register, or of memory, to an unsigned quadword, truncating toward zero whatever MXCSR.RC says: the vector form of C’s cast from double to uint64_t. It is the unsigned partner of VCVTTPD2QQ, which came with it in AVX512DQ, and the vector form of VCVTTSD2USI. A value that truncates to 0 to 2^64 - 1 converts, so -0.5 gives 0; anything else, NaNs and infinities included, gives FFFFFFFFFFFFFFFFh and sets IE. VCVTPD2UQQ rounds instead, and VCVTTPD2UDQ converts to doublewords.

Recorded on Zen 5

  • Infinities. {evex} vcvttpd2uqq xmm5, xmm5 turned +infinity and -infinity both into FFFFFFFFFFFFFFFFh and set IE.
  • 2^63 is valid. 2^63 gave 8000000000000000h, the signed conversion’s indefinite value and here an ordinary result, while a double near 10^300 gave FFFFFFFFFFFFFFFFh with IE.
  • With {sae}. In vcvttpd2uqq zmm5{k5}, zmm5, {sae}, with IE unmasked, the double just below 2^31 gave 7FFFFFFFh, 1.0000000000000002 gave 1 and -2^63 gave FFFFFFFFFFFFFFFFh, without a fault or a flag.
  • Precision. A broadcast 0.5 gave 0 and set PE.

In compiled code

At -O2 with -march=x86-64-v4, both compilers vectorize u[i] = (uint64_t)d[i] with VCVTTPD2UQQ, GCC 14 on ZMM registers and Clang 23 on YMM registers, and use it after a rounding instruction for (uint64_t)rint(d[i]). A single cast is VCVTTSD2USI. _mm512_cvttpd_epu64 is one VCVTTPD2UQQ.

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

Forms

Every encoding of VCVTTPD2UQQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTTPD2UQQ xmm {k}{z}, xmm VCVTTPD2UQQ_XMMu64_MASKmskw_XMMf64_AVX512EVEX.128.66.0F.W1 78 /rAVX10.1 or AVX512DQ + AVX512VL
VCVTTPD2UQQ xmm {k}{z}, m128/m64bcst VCVTTPD2UQQ_XMMu64_MASKmskw_MEMf64_AVX512EVEX.128.66.0F.W1 78 /rAVX10.1 or AVX512DQ + AVX512VL
VCVTTPD2UQQ ymm {k}{z}, ymm VCVTTPD2UQQ_YMMu64_MASKmskw_YMMf64_AVX512EVEX.256.66.0F.W1 78 /rAVX10.1 or AVX512DQ + AVX512VL
VCVTTPD2UQQ ymm {k}{z}, m256/m64bcst VCVTTPD2UQQ_YMMu64_MASKmskw_MEMf64_AVX512EVEX.256.66.0F.W1 78 /rAVX10.1 or AVX512DQ + AVX512VL
VCVTTPD2UQQ zmm {k}{z}, zmm, {sae} VCVTTPD2UQQ_ZMMu64_MASKmskw_ZMMf64_AVX512EVEX.512.66.0F.W1 78 /rAVX10.1 or AVX512DQ
VCVTTPD2UQQ zmm {k}{z}, m512/m64bcst VCVTTPD2UQQ_ZMMu64_MASKmskw_MEMf64_AVX512EVEX.512.66.0F.W1 78 /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}, xmm
ymm {k}{z}, ymm
xmm {k}{z}, m128/m64bcstymm {k}{z}, m256/m64bcstzmm {k}{z}, zmm, {sae}no maskzmm {k}{z}, zmm, {sae}with a mask, zeroing, with {sae}zmm {k}{z}, m512/m64bcst
Skylake-SP, Ice Lake4 / 0.5p0110 / 0.5p0111 / 0.5p014 / 0.5p053 / 0.5p0511 / 0.5p01
Sapphire Rapids4 / 0.5p0111 / 0.5p0112 / 0.5p014 / 1p04 / 1p012 / 1p0
Zen 43 / 1FP2 FP310 / 1FP2 FP310 / 1FP2 FP33 / 2FP2 FP33 / 2FP2 FP310 / 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 double of the result comes from the double in the same place in each source.
VCVTTPD2UQQ: element by elementResult double i comes from double i of xmm2. Result doubles 1 to 0: r1, r0.01xmm2or m128a11k1r0r1xmm1

Every double works alike: 2, 4 and 8 doubles 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 double from memory stands for every element of the last source.

Result double i comes from double i of xmm2. Result doubles 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]:
        a = src2.f64[i]
        zmm1.q[i] = cvtt_uint(a, 64)
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src2.f64[i] is the m64 for every i
# {sae}: no exception 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
VCVTTPD2UQQ xmm {k}{z}, xmm/m128/m64bcst VCVTTPD2UQQ ymm {k}{z}, ymm/m256/m64bcst VCVTTPD2UQQ zmm {k}{z}, zmm/m512/m64bcst, {sae}
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 VCVTTPD2UQQ, 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_cvttpd_epu64 __m128i _mm_cvttpd_epu64(__m128d __A)

VCVTTPD2UQQ xmm, xmm EVEX.128 -mavx512vl -mavx512dq

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

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

_mm_maskz_cvttpd_epu64 __m128i _mm_maskz_cvttpd_epu64(__mmask8 __U, __m128d __A)

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

_mm256_cvttpd_epu64 __m256i _mm256_cvttpd_epu64(__m256d __A)

VCVTTPD2UQQ ymm, ymm EVEX.256 -mavx512vl -mavx512dq

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

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

_mm256_maskz_cvttpd_epu64 __m256i _mm256_maskz_cvttpd_epu64(__mmask8 __U, __m256d __A)

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

_mm512_cvtt_roundpd_epu64 __m512i _mm512_cvtt_roundpd_epu64(__m512d A, const int R)

VCVTTPD2UQQ zmm, zmm, {sae} EVEX.512 -mavx512dq

_mm512_cvttpd_epu64 __m512i _mm512_cvttpd_epu64(__m512d __A)

VCVTTPD2UQQ zmm, zmm EVEX.512 -mavx512dq

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

VCVTTPD2UQQ zmm {k}, zmm, {sae} EVEX.512 -mavx512dq

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

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

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

VCVTTPD2UQQ zmm {k}{z}, zmm, {sae} EVEX.512 -mavx512dq

_mm512_maskz_cvttpd_epu64 __m512i _mm512_maskz_cvttpd_epu64(__mmask8 __U, __m512d __A)

VCVTTPD2UQQ 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-105 (VCVTTPD2UQQ)
  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.