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

VCVTTPD2UQQS converts doubles to unsigned quadwords, truncating toward zero, and saturates: 2^64 or more becomes all ones, a value of -1 or less becomes 0, and a NaN becomes 0. VCVTTPD2UQQ gives all ones, the unsigned indefinite, for all of them. Source and result have the same width. It is the unsigned partner of VCVTTPD2QQS: opcode 6Ch in EVEX map 5 with a 66 prefix and W1, part of AVX10.2, with a write mask, a broadcast double and {sae} on the 512-bit form. NaNs, infinities and out-of-range values still set IE, and a lost fraction sets PE.

Why it matters for unsigned types

Before AVX-512 there was no unsigned conversion at all, and compilers built one from signed conversions and a correction; VCVTTPD2UQQ removed that but kept the indefinite. With VCVTTPD2UQQS a language that clamps, as Rust’s as u64 does, needs no fix-up for negative inputs or NaNs.

In our builds

GCC 14 has no AVX10.2 option. Clang 23 with -mavx10.2 compiles _mm512_cvtts_pd_epu64 to vcvttpd2uqqs zmm0, zmm0. The specification’s helper for it (revision 7.0) uses a width it never sets, an omission beside its siblings. No AVX10.2 processor appears in this site’s recorded cases.

Forms

Every encoding of VCVTTPD2UQQS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTTPD2UQQS xmm {k}{z}, xmm VCVTTPD2UQQS_XMMu64_MASKmskw_XMMf64_AVX512EVEX.128.66.MAP5.W1 6C /rAVX10.2
VCVTTPD2UQQS xmm {k}{z}, m128/m64bcst VCVTTPD2UQQS_XMMu64_MASKmskw_MEMf64_AVX512EVEX.128.66.MAP5.W1 6C /rAVX10.2
VCVTTPD2UQQS ymm {k}{z}, ymm VCVTTPD2UQQS_YMMu64_MASKmskw_YMMf64_AVX512EVEX.256.66.MAP5.W1 6C /rAVX10.2
VCVTTPD2UQQS ymm {k}{z}, m256/m64bcst VCVTTPD2UQQS_YMMu64_MASKmskw_MEMf64_AVX512EVEX.256.66.MAP5.W1 6C /rAVX10.2
VCVTTPD2UQQS zmm {k}{z}, zmm, {sae} VCVTTPD2UQQS_ZMMu64_MASKmskw_ZMMf64_AVX512EVEX.512.66.MAP5.W1 6C /rAVX10.2
VCVTTPD2UQQS zmm {k}{z}, m512/m64bcst VCVTTPD2UQQS_ZMMu64_MASKmskw_MEMf64_AVX512EVEX.512.66.MAP5.W1 6C /rAVX10.2

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.
VCVTTPD2UQQS: 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] = cvtts_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

Not run on a processor: none of these processors has AVX10.2.

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
VCVTTPD2UQQS xmm {k}{z}, xmm/m128/m64bcst VCVTTPD2UQQS ymm {k}{z}, ymm/m256/m64bcst VCVTTPD2UQQS 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 VCVTTPD2UQQS, 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_cvtts_pd_epu64 __m128i _mm_cvtts_pd_epu64(__m128d __A)

VCVTTPD2UQQS xmm, xmm EVEX.128 -mavx10.2

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

VCVTTPD2UQQS xmm {k}, xmm EVEX.128 -mavx10.2

_mm_maskz_cvtts_pd_epu64 __m128i _mm_maskz_cvtts_pd_epu64(__mmask8 __U, __m128d __A)

VCVTTPD2UQQS xmm {k}{z}, xmm EVEX.128 -mavx10.2

_mm256_cvtts_pd_epu64 __m256i _mm256_cvtts_pd_epu64(__m256d __A)

VCVTTPD2UQQS ymm, ymm EVEX.256 -mavx10.2

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

VCVTTPD2UQQS ymm {k}, ymm EVEX.256 -mavx10.2

_mm256_maskz_cvtts_pd_epu64 __m256i _mm256_maskz_cvtts_pd_epu64(__mmask8 __U, __m256d __A)

VCVTTPD2UQQS ymm {k}{z}, ymm EVEX.256 -mavx10.2

_mm512_cvtts_pd_epu64 __m512i _mm512_cvtts_pd_epu64(__m512d __A)

VCVTTPD2UQQS zmm, zmm EVEX.512 -mavx10.2

_mm512_cvtts_roundpd_epu64 __m512i _mm512_cvtts_roundpd_epu64(__m512d __A, const int __R)

VCVTTPD2UQQS zmm, zmm, {sae} EVEX.512 -mavx10.2

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

VCVTTPD2UQQS zmm {k}, zmm EVEX.512 -mavx10.2

_mm512_mask_cvtts_roundpd_epu64 __m512i _mm512_mask_cvtts_roundpd_epu64(__m512i __W, __mmask8 __U, __m512d __A, const int __R)

VCVTTPD2UQQS zmm {k}, zmm, {sae} EVEX.512 -mavx10.2

_mm512_maskz_cvtts_pd_epu64 __m512i _mm512_maskz_cvtts_pd_epu64(__mmask8 __U, __m512d __A)

VCVTTPD2UQQS zmm {k}{z}, zmm EVEX.512 -mavx10.2

_mm512_maskz_cvtts_roundpd_epu64 __m512i _mm512_maskz_cvtts_roundpd_epu64(__mmask8 __U, __m512d __A, const int __R)

VCVTTPD2UQQS zmm {k}{z}, zmm, {sae} EVEX.512 -mavx10.2

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_SAT_CVT_DS_128

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

Nova Lake, Diamond Rapids
AVX512_SAT_CVT_DS_256
Same as AVX512_SAT_CVT_DS_128Same as AVX512_SAT_CVT_DS_128
AVX512_SAT_CVT_DS_512
Same as AVX512_SAT_CVT_DS_128Same as AVX512_SAT_CVT_DS_128

More AVX10.2 instructions

All 96 AVX10.2 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. 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.
  3. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)

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, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.