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

VCVTUDQ2PD converts unsigned doublewords to doubles: 8 from a YMM register or memory fill a ZMM register, 4 fill a YMM register and 2 an XMM register. A double has a 53-bit significand, so every 32-bit unsigned integer converts exactly; the instruction never rounds and sets no MXCSR flag. It is the unsigned partner of VCVTDQ2PD, and the difference shows from 80000000h up: VCVTDQ2PD reads that as -2^31, VCVTUDQ2PD as 2^31. VCVTUDQ2PS converts the same input to singles, which do round. It came with AVX512F.

Recorded on Zen 5

  • Exact values. 80000000h gave 2^31, 7FFFFFFFh gave 2,147,483,647.0, and 01000001h and 01000003h, which singles cannot hold, gave 16,777,217.0 and 16,777,219.0. MXCSR stayed as it was in all six cases.
  • One register both ways. In vcvtudq2pd zmm9{k1}, ymm9, elements 5 and 7, selected by K1, became 1.0 and 2^31 from doublewords 1 and 80000000h, and the unselected elements, which hold the source doublewords, kept their bits.
  • Zeroing. A broadcast of 01000003h to XMM9 under a zero mask that selected both elements gave two copies, and the register was cleared above bit 127.

In compiled code

At -O2 with -march=x86-64-v4, Clang 23 compiles d[i] = u[i] from uint32_t to double into VCVTUDQ2PD from memory on YMM registers. GCC 14 does not use it: it converts with the signed VCVTDQ2PD and adds 2^32 under a mask where the result is negative, found with VCMPPD. _mm512_cvtepu32_pd is one VCVTUDQ2PD in both.

AMD’s Zen 5 latency spreadsheet gives the XMM form one macro-op and 3 cycles, the YMM form from a register two macro-ops and 4 cycles but from memory one and 3, and the ZMM form two macro-ops and 6 cycles.

Forms

Every encoding of VCVTUDQ2PD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTUDQ2PD zmm {k}{z}, ymm VCVTUDQ2PD_ZMMf64_MASKmskw_YMMu32_AVX512EVEX.512.F3.0F.W0 7A /r
EVEX.LIG.F3.0F.W0 7A /r
AVX10.1 or AVX512F
VCVTUDQ2PD zmm {k}{z}, m256/m32bcst VCVTUDQ2PD_ZMMf64_MASKmskw_MEMu32_AVX512EVEX.512.F3.0F.W0 7A /rAVX10.1 or AVX512F
VCVTUDQ2PD xmm {k}{z}, xmm VCVTUDQ2PD_XMMf64_MASKmskw_XMMu32_AVX512EVEX.128.F3.0F.W0 7A /rAVX10.1 or AVX512F + AVX512VL
VCVTUDQ2PD xmm {k}{z}, m64/m32bcst VCVTUDQ2PD_XMMf64_MASKmskw_MEMu32_AVX512EVEX.128.F3.0F.W0 7A /rAVX10.1 or AVX512F + AVX512VL
VCVTUDQ2PD ymm {k}{z}, xmm VCVTUDQ2PD_YMMf64_MASKmskw_XMMu32_AVX512EVEX.256.F3.0F.W0 7A /rAVX10.1 or AVX512F + AVX512VL
VCVTUDQ2PD ymm {k}{z}, m128/m32bcst VCVTUDQ2PD_YMMf64_MASKmskw_MEMu32_AVX512EVEX.256.F3.0F.W0 7A /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.
Modelzmm {k}{z}, ymmno maskzmm {k}{z}, ymmwith a mask, zeroingzmm {k}{z}, m256/m32bcstxmm {k}{z}, xmmxmm {k}{z}, m64/m32bcstymm {k}{z}, xmmymm {k}{z}, m128/m32bcst
Skylake-SP, Ice Lake7 / 1p054 / 0.5p0511 / 0.5p015 / 1p01510 / 0.5p017 / 1p01511 / 0.5p01
Sapphire Rapids7 / 1p057 / 1p0512 / 1p05 / 1p01511 / 0.5p017 / 1p01512 / 0.5p01
Zen 44 / 2FP2 FP34 / 2FP2 FP311 / 2FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 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.

Widen: each doubleword becomes a double, converted, in the same order.
VCVTUDQ2PD: each element widenedResult doubles 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 doublewords. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result doubles 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]:
        zmm1.f64[i] = to_f64(src2.d[i])
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[i] keeps its value
# m32bcst: src2.d[i] is the m32 for every i
# 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
VCVTUDQ2PD xmm {k}{z}, xmm/m64/m32bcst VCVTUDQ2PD ymm {k}{z}, xmm/m128/m32bcst VCVTUDQ2PD zmm {k}{z}, ymm/m256/m32bcst
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-E5

Attributes

What else XED records about the forms. How to read.

All forms
write masking
Memory forms
embedded broadcast (tuple Half); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTUDQ2PD, 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_cvtepu32_pd __m128d _mm_cvtepu32_pd(__m128i __A)

VCVTUDQ2PD xmm, xmm EVEX.128 -mavx512vl

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

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

_mm_maskz_cvtepu32_pd __m128d _mm_maskz_cvtepu32_pd(__mmask8 __U, __m128i __A)

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

_mm256_cvtepu32_pd __m256d _mm256_cvtepu32_pd(__m128i __A)

VCVTUDQ2PD ymm, xmm EVEX.256 -mavx512vl

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

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

_mm256_maskz_cvtepu32_pd __m256d _mm256_maskz_cvtepu32_pd(__mmask8 __U, __m128i __A)

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

_mm512_cvtepu32_pd __m512d _mm512_cvtepu32_pd(__m256i __A)

VCVTUDQ2PD zmm, ymm EVEX.512 -mavx512f

_mm512_cvtepu32lo_pd __m512d _mm512_cvtepu32lo_pd(__m512i __A)

VCVTUDQ2PD zmm, ymm EVEX.512 -mavx512f

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

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

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

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

_mm512_maskz_cvtepu32_pd __m512d _mm512_maskz_cvtepu32_pd(__mmask8 __U, __m256i __A)

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