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

VCVTUDQ2PS converts unsigned doublewords to singles, 4, 8 or 16 at a time. It is the unsigned partner of CVTDQ2PS, whose page explains the rounding of integers above 2^24 and the workarounds for unsigned input before AVX-512; this one needs none of them. The difference shows from 80000000h up: VCVTDQ2PS reads FFFFFFFFh as -1 and gives -1.0, VCVTUDQ2PS reads it as 4,294,967,295.

Rounding near the top

That largest input lies between two singles, 4,294,967,040 (4F7FFFFFh) and 2^32, so the rounding mode decides, and a result of 2^32 is outside the range of uint32_t when converted back. The cases recorded on Zen 5 show the modes at work:

  • FFFFFFFFh and FFFFFFFEh rounded toward zero or down gave 4,294,967,040;
  • 7FFFFFFFh rounded up gave 2^31, and 01000001h (2^24 + 1) rounded up gave 2^24 + 2;
  • 80000000h, FFFFFFh and 1 converted exactly.

The inexact ones set PE. The 512-bit register form takes {er}, a rounding mode for this instruction alone that also keeps MXCSR’s flags as they are: a recorded case with {rz-sae} left MXCSR unchanged. Like other AVX-512 conversions it takes a write mask with merging or zeroing, and a 32-bit broadcast from memory.

In compiled code

For d[i] = a[i] from uint32_t to float, Clang 23 at -O2 with -march=x86-64-v4 emits one VCVTUDQ2PS per 8 elements on YMM registers, and VCVTUSI2SS for the last few. With -march=x86-64-v3 it builds the result from the two 16-bit halves of each element with VPBLENDW, VSUBPS and VADDPS, the AVX2 version of the trick on the CVTDQ2PS page. GCC 14 keeps the loop scalar at -O2, with one VCVTUSI2SS per element under x86-64-v4. The intrinsics are _mm512_cvtepu32_ps and its masked, rounding and narrower kin.

VCVTUDQ2PD converts to doubles, which hold every 32-bit integer exactly, and VCVTPS2UDQ goes the other way.

Forms

Every encoding of VCVTUDQ2PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTUDQ2PS zmm {k}{z}, zmm, {er} VCVTUDQ2PS_ZMMf32_MASKmskw_ZMMu32_AVX512EVEX.512.F2.0F.W0 7A /rAVX10.1 or AVX512F
VCVTUDQ2PS zmm {k}{z}, m512/m32bcst VCVTUDQ2PS_ZMMf32_MASKmskw_MEMu32_AVX512EVEX.512.F2.0F.W0 7A /rAVX10.1 or AVX512F
VCVTUDQ2PS xmm {k}{z}, xmm VCVTUDQ2PS_XMMf32_MASKmskw_XMMu32_AVX512EVEX.128.F2.0F.W0 7A /rAVX10.1 or AVX512F + AVX512VL
VCVTUDQ2PS xmm {k}{z}, m128/m32bcst VCVTUDQ2PS_XMMf32_MASKmskw_MEMu32_AVX512EVEX.128.F2.0F.W0 7A /rAVX10.1 or AVX512F + AVX512VL
VCVTUDQ2PS ymm {k}{z}, ymm VCVTUDQ2PS_YMMf32_MASKmskw_YMMu32_AVX512EVEX.256.F2.0F.W0 7A /rAVX10.1 or AVX512F + AVX512VL
VCVTUDQ2PS ymm {k}{z}, m256/m32bcst VCVTUDQ2PS_YMMf32_MASKmskw_MEMu32_AVX512EVEX.256.F2.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}, zmm, {er}zmm {k}{z}, m512/m32bcstxmm {k}{z}, xmm
ymm {k}{z}, ymm
xmm {k}{z}, m128/m32bcstymm {k}{z}, m256/m32bcst
Skylake-SP, Ice Lake4 / 0.5p0511 / 0.5p014 / 0.5p0110 / 0.5p0111 / 0.5p01
Sapphire Rapids4 / 1p012 / 1p04 / 0.5p0111 / 0.5p0112 / 0.5p01
Zen 43 / 1FP2 FP310 / 1FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP310 / 0.5FP2 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 doubleword of the result comes from the doubleword in the same place in each source.
VCVTUDQ2PS: element by elementResult doubleword i comes from doubleword i of xmm2. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2or m128a1110k1r0r1r3xmm1

Every doubleword works alike: 4, 8 and 16 doublewords 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 m32bcst, one doubleword from memory stands for every element of the last source.

Result doubleword i comes from doubleword i of xmm2. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 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 // 32):
    if k1[i]:
        zmm1.f32[i] = to_f32(src2.d[i])
    elif zeroing:
        zmm1.f32[i] = 0
    # else: zmm1.f32[i] keeps its value
# m32bcst: src2.d[i] is the m32 for every i
# {er}: the form's rounding, not MXCSR.RC, and no 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
VCVTUDQ2PS xmm {k}{z}, xmm/m128/m32bcst VCVTUDQ2PS ymm {k}{z}, ymm/m256/m32bcst VCVTUDQ2PS zmm {k}{z}, zmm/m512/m32bcst, {er}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/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 Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTUDQ2PS, 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_ps __m128 _mm_cvtepu32_ps(__m128i __A)

VCVTUDQ2PS xmm, xmm EVEX.128 -mavx512vl

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

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

_mm_maskz_cvtepu32_ps __m128 _mm_maskz_cvtepu32_ps(__mmask8 __U, __m128i __A)

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

_mm256_cvtepu32_ps __m256 _mm256_cvtepu32_ps(__m256i __A)

VCVTUDQ2PS ymm, ymm EVEX.256 -mavx512vl

_mm256_mask_cvtepu32_ps __m256 _mm256_mask_cvtepu32_ps(__m256 __W, __mmask8 __U, __m256i __A)

VCVTUDQ2PS ymm {k}, ymm EVEX.256 -mavx512vl

_mm256_maskz_cvtepu32_ps __m256 _mm256_maskz_cvtepu32_ps(__mmask8 __U, __m256i __A)

VCVTUDQ2PS ymm {k}{z}, ymm EVEX.256 -mavx512vl

_mm512_cvt_roundepu32_ps __m512 _mm512_cvt_roundepu32_ps(__m512i A, const int R)

VCVTUDQ2PS zmm, zmm, {er} EVEX.512 -mavx512f

_mm512_cvtepu32_ps __m512 _mm512_cvtepu32_ps(__m512i __A)

VCVTUDQ2PS zmm, zmm EVEX.512 -mavx512f

_mm512_mask_cvt_roundepu32_ps __m512 _mm512_mask_cvt_roundepu32_ps(__m512 W, __mmask16 U, __m512i A, const int R)

VCVTUDQ2PS zmm {k}, zmm, {er} EVEX.512 -mavx512f

_mm512_mask_cvtepu32_ps __m512 _mm512_mask_cvtepu32_ps(__m512 __W, __mmask16 __U, __m512i __A)

VCVTUDQ2PS zmm {k}, zmm EVEX.512 -mavx512f

_mm512_maskz_cvt_roundepu32_ps __m512 _mm512_maskz_cvt_roundepu32_ps(__mmask16 U, __m512i A, const int R)

VCVTUDQ2PS zmm {k}{z}, zmm, {er} EVEX.512 -mavx512f

_mm512_maskz_cvtepu32_ps __m512 _mm512_maskz_cvtepu32_ps(__mmask16 __U, __m512i __A)

VCVTUDQ2PS zmm {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-135 (VCVTUDQ2PS)

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.