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

VCVTTPD2UDQ truncates doubles toward zero to unsigned doublewords: 8 doubles of a ZMM register become 8 doublewords in a YMM register, 4 fill an XMM register and 2 fill its low 64 bits, with the rest of the destination cleared. It is the unsigned partner of VCVTTPD2DQ, with the range 0 to 2^32 - 1 and FFFFFFFFh as the indefinite value, and the double-precision sibling of VCVTTPS2UDQ. It came with AVX512F; the 512-bit register form takes {sae}.

Recorded on Zen 5

  • Truncation. 4.0, 1.5, 3.0, 0.5 and 0.1 gave 4, 1, 3, 0 and 0; -2.5 gave FFFFFFFFh, since it truncates to -2, which is out of range.
  • The same bits, two meanings. 2^32 - 0.5 gave FFFFFFFFh as a valid result, setting only PE; a huge double and a quiet NaN gave the same FFFFFFFFh as the indefinite and set IE. 2^31 minus a tiny fraction gave 7FFFFFFFh.
  • The upper part. The XMM form, {evex} vcvttpd2udq xmm0, xmm31, wrote its two doublewords and cleared XMM0 from bit 64 up.

In compiled code

At -O2 with -march=x86-64-v4, GCC 14 and Clang 23 compile u[i] = (uint32_t)d[i] to VCVTTPD2UDQ from memory. GCC converts two ZMM loads to YMM halves and joins them with VINSERTI32X8; Clang converts YMM loads to XMM registers and stores each. _mm512_cvttpd_epu32 is the ZMM form. With -march=x86-64-v3 both build the conversion from VCVTTPD2DQ, converting a second time after subtracting 2^31 with VSUBPD and merging the two results, as for singles on VCVTTPS2UDQ’s page.

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

Forms

Every encoding of VCVTTPD2UDQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTTPD2UDQ ymm {k}{z}, zmm, {sae} VCVTTPD2UDQ_YMMu32_MASKmskw_ZMMf64_AVX512_VL512EVEX.512.NP.0F.W1 78 /rAVX10.1 or AVX512F
VCVTTPD2UDQ ymm {k}{z}, m512/m64bcst VCVTTPD2UDQ_YMMu32_MASKmskw_MEMf64_AVX512_VL512EVEX.512.NP.0F.W1 78 /rAVX10.1 or AVX512F
VCVTTPD2UDQ xmm {k}{z}, xmm VCVTTPD2UDQ_XMMu32_MASKmskw_XMMf64_AVX512_VL128EVEX.128.NP.0F.W1 78 /rAVX10.1 or AVX512F + AVX512VL
VCVTTPD2UDQ xmm {k}{z}, m128/m64bcst VCVTTPD2UDQ_XMMu32_MASKmskw_MEMf64_AVX512_VL128EVEX.128.NP.0F.W1 78 /rAVX10.1 or AVX512F + AVX512VL
VCVTTPD2UDQ xmm {k}{z}, ymm VCVTTPD2UDQ_XMMu32_MASKmskw_YMMf64_AVX512_VL256EVEX.256.NP.0F.W1 78 /rAVX10.1 or AVX512F + AVX512VL
VCVTTPD2UDQ xmm {k}{z}, m256/m64bcst VCVTTPD2UDQ_XMMu32_MASKmskw_MEMf64_AVX512_VL256EVEX.256.NP.0F.W1 78 /rAVX10.1 or AVX512F + AVX512VL

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.
Modelymm {k}{z}, zmm, {sae}no maskymm {k}{z}, zmm, {sae}with a mask, zeroing, with {sae}ymm {k}{z}, m512/m64bcstxmm {k}{z}, xmmxmm {k}{z}, m128/m64bcstxmm {k}{z}, ymmxmm {k}{z}, m256/m64bcst
Skylake-SP, Ice Lake7 / 1p053 / 0.5p0514 / 1p0155 / 1p0158 / 0.5p017 / 1p0158 / 0.5p01
Sapphire Rapids7 / 1p057 / 1p0515 / 1p055 / 1p01512 / 1p0157 / 1p01515 / 1p015
Zen 43 / 2FP2 FP33 / 2FP2 FP310 / 2FP2 FP33 / 1FP2 FP310 / 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 double becomes a doubleword, in the same order, at the low end of the result.
VCVTTPD2UDQ: each element narrowedResult doublewords 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 doubles. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result doublewords 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.f64[i]
        ymm1.d[i] = cvtt_uint(a, 32)
    elif zeroing:
        ymm1.d[i] = 0
    # else: ymm1.d[i] keeps its value
for i in range(VL // 64, 4):
    ymm1.d[i] = 0
# m64bcst: src2.f64[i] is the m64 for every i
# {sae}: no exception 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
VCVTTPD2UDQ xmm {k}{z}, xmm/m128/m64bcst VCVTTPD2UDQ xmm {k}{z}, ymm/m256/m64bcst VCVTTPD2UDQ ymm {k}{z}, zmm/m512/m64bcst, {sae}
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 VCVTTPD2UDQ, 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_epu32 __m128i _mm_cvttpd_epu32(__m128d __A)

VCVTTPD2UDQ xmm, xmm EVEX.128 -mavx512vl

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

VCVTTPD2UDQ xmm {k}, xmm EVEX.128 -mavx512vl

_mm_maskz_cvttpd_epu32 __m128i _mm_maskz_cvttpd_epu32(__mmask8 __U, __m128d __A)

VCVTTPD2UDQ xmm {k}{z}, xmm EVEX.128 -mavx512vl

_mm256_cvttpd_epu32 __m128i _mm256_cvttpd_epu32(__m256d __A)

VCVTTPD2UDQ xmm, ymm EVEX.256 -mavx512vl

_mm256_mask_cvttpd_epu32 __m128i _mm256_mask_cvttpd_epu32(__m128i __W, __mmask8 __U, __m256d __A)

VCVTTPD2UDQ xmm {k}, ymm EVEX.256 -mavx512vl

_mm256_maskz_cvttpd_epu32 __m128i _mm256_maskz_cvttpd_epu32(__mmask8 __U, __m256d __A)

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

_mm512_cvtt_roundpd_epu32 __m256i _mm512_cvtt_roundpd_epu32(__m512d A, const int R)

VCVTTPD2UDQ ymm, zmm, {sae} EVEX.512 -mavx512f

_mm512_cvttpd_epu32 __m256i _mm512_cvttpd_epu32(__m512d __A)

VCVTTPD2UDQ ymm, zmm EVEX.512 -mavx512f

_mm512_mask_cvtt_roundpd_epu32 __m256i _mm512_mask_cvtt_roundpd_epu32(__m256i W, __mmask8 U, __m512d A, const int R)

VCVTTPD2UDQ ymm {k}, zmm, {sae} EVEX.512 -mavx512f

_mm512_mask_cvttpd_epu32 __m256i _mm512_mask_cvttpd_epu32(__m256i __W, __mmask8 __U, __m512d __A)

VCVTTPD2UDQ ymm {k}, zmm EVEX.512 -mavx512f

_mm512_maskz_cvtt_roundpd_epu32 __m256i _mm512_maskz_cvtt_roundpd_epu32(__mmask8 U, __m512d A, const int R)

VCVTTPD2UDQ ymm {k}{z}, zmm, {sae} EVEX.512 -mavx512f

_mm512_maskz_cvttpd_epu32 __m256i _mm512_maskz_cvttpd_epu32(__mmask8 __U, __m512d __A)

VCVTTPD2UDQ ymm {k}{z}, zmm EVEX.512 -mavx512f

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
AVX512F_512

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

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F

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, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512F_128

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

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
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
AVX512F_256
Same as AVX512F_128Same as AVX512F_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-103 (VCVTTPD2UDQ)
  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.