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

VCVTTPS2UQQ converts singles to unsigned quadwords, 2, 4 or 8 at a time into an XMM, YMM or ZMM register, truncating toward zero whatever MXCSR.RC says: the vector form of C’s cast from float to uint64_t. It is the unsigned partner of VCVTTPS2QQ, which came with it in AVX512DQ, the truncating form of VCVTPS2UQQ and the quadword form of VCVTTPS2UDQ. A value that truncates to 0 to 2^64 - 1 converts, so -0.5 gives 0; a negative value of -1 or less, a NaN, an infinity or a value of 2^64 or more gives FFFFFFFFFFFFFFFFh and sets IE.

Recorded on Zen 5

  • Negative values. A broadcast -1.5 gave FFFFFFFFFFFFFFFFh in both elements of vcvttps2uqq xmm7{k7}{z}, dword bcst [...] and set IE, as did -2^31.
  • Large singles. 4EFFFFFFh, the largest single below 2^31, gave 7FFFFF80h, from a register and from memory.
  • DAZ. With DAZ set, the smallest and the largest denormal both gave 0, without PE: the inputs count as zeros, which convert exactly.
  • With {sae}. In vcvttps2uqq zmm14{k4}, ymm8, {sae}, with IE unmasked, -1.0 and -2.5 gave FFFFFFFFFFFFFFFFh, while 4.0, 1.5 and 2.5 gave 4, 1 and 2, without a fault or a flag.

In compiled code

At -O2 with -march=x86-64-v4, both compilers vectorize u[i] = (uint64_t)f[i] with VCVTTPS2UQQ, GCC 14 on ZMM registers and Clang 23 on YMM registers, 4 singles at a time from memory, as for the signed cast. A single cast is VCVTTSS2USI. _mm512_cvttps_epu64 is one VCVTTPS2UQQ.

AMD’s Zen 5 latency spreadsheet gives the same rows as for VCVTTPS2QQ: 3 cycles for the XMM form, 4 for the YMM form from a register and 6 for the ZMM form, with one macro-op from memory at YMM width.

Forms

Every encoding of VCVTTPS2UQQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTTPS2UQQ xmm {k}{z}, xmm VCVTTPS2UQQ_XMMu64_MASKmskw_XMMf32_AVX512EVEX.128.66.0F.W0 78 /rAVX10.1 or AVX512DQ + AVX512VL
VCVTTPS2UQQ xmm {k}{z}, m64/m32bcst VCVTTPS2UQQ_XMMu64_MASKmskw_MEMf32_AVX512EVEX.128.66.0F.W0 78 /rAVX10.1 or AVX512DQ + AVX512VL
VCVTTPS2UQQ ymm {k}{z}, xmm VCVTTPS2UQQ_YMMu64_MASKmskw_XMMf32_AVX512EVEX.256.66.0F.W0 78 /rAVX10.1 or AVX512DQ + AVX512VL
VCVTTPS2UQQ ymm {k}{z}, m128/m32bcst VCVTTPS2UQQ_YMMu64_MASKmskw_MEMf32_AVX512EVEX.256.66.0F.W0 78 /rAVX10.1 or AVX512DQ + AVX512VL
VCVTTPS2UQQ zmm {k}{z}, ymm, {sae} VCVTTPS2UQQ_ZMMu64_MASKmskw_YMMf32_AVX512EVEX.512.66.0F.W0 78 /rAVX10.1 or AVX512DQ
VCVTTPS2UQQ zmm {k}{z}, m256/m32bcst VCVTTPS2UQQ_ZMMu64_MASKmskw_MEMf32_AVX512EVEX.512.66.0F.W0 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}, xmmxmm {k}{z}, m64/m32bcstymm {k}{z}, xmmymm {k}{z}, m128/m32bcstzmm {k}{z}, ymm, {sae}no maskzmm {k}{z}, ymm, {sae}with a mask, zeroing, with {sae}zmm {k}{z}, m256/m32bcst
Skylake-SP, Ice Lake5 / 1p01510 / 0.5p017 / 1p01511 / 0.5p017 / 1p053 / 0.5p0512 / 1p015
Sapphire Rapids5 / 1p01511 / 0.5p017 / 1p01512 / 0.5p017 / 1p057 / 1p0513 / 1p05
Zen 43 / 0.5FP2 FP310 / 0.5FP2 FP34 / 0.5FP2 FP311 / 0.5FP2 FP34 / 1FP2 FP34 / 1FP2 FP311 / 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.

Widen: each single becomes a quadword, converted, in the same order.
VCVTTPS2UQQ: each element widenedResult quadwords 7 to 0: a7, unchanged (bit 6 of k1 is 0), a5, a4, a3, a2, a1, a0.01234567ymm2or m256a11111110k1a0a1a2a3a4a5a7zmm1

Shown for the zmm form; the xmm and ymm forms work the same on 2 and 4 singles. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result quadwords 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]:
        a = src2.f32[i]
        zmm1.q[i] = cvtt_uint(a, 64)
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m32bcst: src2.f32[i] is the m32 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
VCVTTPS2UQQ xmm {k}{z}, xmm/m64/m32bcst VCVTTPS2UQQ ymm {k}{z}, xmm/m128/m32bcst VCVTTPS2UQQ zmm {k}{z}, ymm/m256/m32bcst, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m64/m32bcst, xmm/m128/m32bcst, ymm/m256/m32bcstexplicitread

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 Half); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTTPS2UQQ, 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_cvttps_epu64 __m128i _mm_cvttps_epu64(__m128 __A)

VCVTTPS2UQQ xmm, xmm EVEX.128 -mavx512vl -mavx512dq

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

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

_mm_maskz_cvttps_epu64 __m128i _mm_maskz_cvttps_epu64(__mmask8 __U, __m128 __A)

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

_mm256_cvttps_epu64 __m256i _mm256_cvttps_epu64(__m128 __A)

VCVTTPS2UQQ ymm, xmm EVEX.256 -mavx512vl -mavx512dq

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

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

_mm256_maskz_cvttps_epu64 __m256i _mm256_maskz_cvttps_epu64(__mmask8 __U, __m128 __A)

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

_mm512_cvtt_roundps_epu64 __m512i _mm512_cvtt_roundps_epu64(__m256 A, const int R)

VCVTTPS2UQQ zmm, ymm, {sae} EVEX.512 -mavx512dq

_mm512_cvttps_epu64 __m512i _mm512_cvttps_epu64(__m256 __A)

VCVTTPS2UQQ zmm, ymm EVEX.512 -mavx512dq

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

VCVTTPS2UQQ zmm {k}, ymm, {sae} EVEX.512 -mavx512dq

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

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

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

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

_mm512_maskz_cvttps_epu64 __m512i _mm512_maskz_cvttps_epu64(__mmask8 __U, __m256 __A)

VCVTTPS2UQQ zmm {k}{z}, ymm 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-123 (VCVTTPS2UQQ)
  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.