Extensions
Forms
10 (4 VEX, 6 EVEX)
Data
Intel XED v2026.08.23

VCVTDQ2PD converts signed doublewords to doubles, always exactly: four from an xmm register or 16 bytes into a ymm register with VEX, eight from a ymm register into a zmm one with EVEX. CVTDQ2PD explains why no rounding or flag is possible and how compilers widen an array in halves, and VCVTDQ2PS is the conversion to singles, which does round. Being exact, the EVEX form takes neither a rounding mode nor {sae}; what it adds is masking per double and a broadcast doubleword.

Exact where singles are not

The cases recorded on Zen 5 show integers that a single cannot hold: 16,777,217, 16,777,219 and 2,147,483,647 came back as themselves, as did -2,147,483,647 and -2^31 in the EVEX form. MXCSR came back unchanged in every case, whatever its rounding field said.

Masks per double

Each mask bit selects one result double. With E1H in the low byte of K5, vcvtdq2pd zmm14{k5}, ymm8 wrote doubles 0, 5, 6 and 7 and kept the other four; the 256-bit form with a memory source and the same mask wrote only double 0, since it uses only the mask’s low four bits.

Unsigned integers

For unsigned elements the signed conversion is wrong from 2^31 up, and our builds at -O2 handle that in three ways. For -march=x86-64-v3, GCC 14 converts as signed, compares the results with zero and adds 2^32 to the negative ones through an AND mask, and Clang 23 zero-extends with VPMOVZXDQ and places the integers in the significand of 2^52 before subtracting it. For x86-64-v4, GCC keeps VCVTDQ2PD on zmm registers but compares into a mask register with VCMPPD and adds 2^32 with a masked VADDPD, while Clang switches to AVX-512’s VCVTUDQ2PD.

For signed integers, GCC widens a loaded vector in two halves around VEXTRACTI128 (VEXTRACTI32X8 for x86-64-v4), and Clang converts straight from memory, to ymm registers for x86-64-v3 and x86-64-v4 and to zmm for znver5.

In the optimization guide

What the optimization guide says about VCVTDQ2PD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Crestmont and Gracemont

  • Vectors and AVX2: The 256-bit forms that widen or insert data loaded from memory take two dependent micro-ops.

Forms

Every encoding of VCVTDQ2PD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTDQ2PD xmm, m64 VCVTDQ2PD_XMMdq_MEMqVEX.128.F3.0F.WIG E6 /rAVX
VCVTDQ2PD xmm, xmm VCVTDQ2PD_XMMdq_XMMqVEX.128.F3.0F.WIG E6 /rAVX
VCVTDQ2PD ymm, m128 VCVTDQ2PD_YMMqq_MEMdqVEX.256.F3.0F.WIG E6 /rAVX
VCVTDQ2PD ymm, xmm VCVTDQ2PD_YMMqq_XMMdqVEX.256.F3.0F.WIG E6 /rAVX
VCVTDQ2PD zmm {k}{z}, ymm VCVTDQ2PD_ZMMf64_MASKmskw_YMMi32_AVX512EVEX.512.F3.0F.W0 E6 /r
EVEX.LIG.F3.0F.W0 E6 /r
AVX10.1 or AVX512F
VCVTDQ2PD zmm {k}{z}, m256/m32bcst VCVTDQ2PD_ZMMf64_MASKmskw_MEMi32_AVX512EVEX.512.F3.0F.W0 E6 /rAVX10.1 or AVX512F
VCVTDQ2PD xmm {k}{z}, xmm VCVTDQ2PD_XMMf64_MASKmskw_XMMi32_AVX512EVEX.128.F3.0F.W0 E6 /rAVX10.1 or AVX512F + AVX512VL
VCVTDQ2PD xmm {k}{z}, m64/m32bcst VCVTDQ2PD_XMMf64_MASKmskw_MEMi32_AVX512EVEX.128.F3.0F.W0 E6 /rAVX10.1 or AVX512F + AVX512VL
VCVTDQ2PD ymm {k}{z}, xmm VCVTDQ2PD_YMMf64_MASKmskw_XMMi32_AVX512EVEX.256.F3.0F.W0 E6 /rAVX10.1 or AVX512F + AVX512VL
VCVTDQ2PD ymm {k}{z}, m128/m32bcst VCVTDQ2PD_YMMf64_MASKmskw_MEMi32_AVX512EVEX.256.F3.0F.W0 E6 /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.
Modelxmm, m64xmm, xmmymm, m128ymm, xmm
ymm {k}{z}, xmm
zmm {k}{z}, ymmno maskzmm {k}{z}, ymmwith a mask, zeroingzmm {k}{z}, m256/m32bcstxmm {k}{z}, xmmxmm {k}{z}, m64/m32bcstymm {k}{z}, m128/m32bcst
Sandy Bridge10 / 1p154 / 1p1510 / 1p154 / 1p15
Haswell10 / 1p14 / 1p1512 / 1p16 / 1p15
Broadwell9 / 1p14 / 1p1511 / 1p16 / 1p15
Skylake10 / 0.5p015 / 1p01511 / 0.5p017 / 1p015
Skylake-SP, Ice Lake11 / 1p054 / 0.5p0113 / 1p057 / 1p0157 / 1p054 / 0.5p0511 / 0.5p015 / 1p01510 / 0.5p0111 / 0.5p01
Alder Lake11 / 0.5p015 / 1p01512 / 0.5p017 / 1p015
Sapphire Rapids11 / 0.5p015 / 1p01512 / 0.5p017 / 1p0157 / 1p057 / 1p0512 / 1p05 / 1p01511 / 0.5p0112 / 0.5p01
Lunar Lake11 / 0.5V0 V15 / 0.5V0 V1 V2 V311 / 2.33V0 V17 / 2V0 V1 V2 V3
Piledriver13 / 1.5FPCVT FPU08 / 1FPCVT FPSTO FPU013 / 2FPCVT FPU08 / 2FPCVT FPSTO FPU0
Zen12 / 1FPU35 / 1FPU1 FPU2 FPU312 / 1FPU35 / 1FPU1 FPU2 FPU3
Zen 212 / 1FPU33 / 1FPU1 FPU2 FPU312 / 1FPU33 / 1FPU1 FPU2 FPU3
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP311 / 1FP2 FP34 / 1FP2 FP3
Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP310 / 1FP2 FP33 / 11FP2 FP34 / 22FP2 FP34 / 22FP2 FP311 / 2FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP310 / 1FP2 FP3
Jaguar8 / 1FPU13 / 1FPU1 STC8 / 2FPU13 / 2FPU1 STC
  1. Zen 4 model: AMD's spreadsheets give latency 4 for Zen 4 and Zen 5 (AMD 57647, row 967; AMD 58455, row 29).
  2. Zen 4 model: AMD's spreadsheets give latency 6 for Zen 4 and Zen 5 (AMD 57647, row 969; AMD 58455, row 31).

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.
VCVTDQ2PD: 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 EVEX 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]:  # 1 without a write mask
        zmm1.f64[i] = to_f64(src2.sd[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): 15 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
VCVTDQ2PD xmm, xmm/m64 VCVTDQ2PD ymm, xmm/m128
xmm, ymmexplicitwrite
xmm/m64/128explicitread
VCVTDQ2PD xmm {k}{z}, xmm/m64/m32bcst VCVTDQ2PD ymm {k}{z}, xmm/m128/m32bcst VCVTDQ2PD 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.

VEX forms
avx-type-5
EVEX forms
AVX512-E5

Attributes

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

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

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTDQ2PD, 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_cvtepi32_pd __m128d _mm_cvtepi32_pd(__m128i __a)

VCVTDQ2PD xmm, xmm VEX.128 -mavxwith AVX enabled

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

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

_mm_maskz_cvtepi32_pd __m128d _mm_maskz_cvtepi32_pd(__mmask8 __U, __m128i __A)

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

_mm256_cvtepi32_pd __m256d _mm256_cvtepi32_pd(__m128i __a)

VCVTDQ2PD ymm, xmm VEX.256 -mavx

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

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

_mm256_maskz_cvtepi32_pd __m256d _mm256_maskz_cvtepi32_pd(__mmask8 __U, __m128i __A)

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

_mm512_cvtepi32_pd __m512d _mm512_cvtepi32_pd(__m256i __A)

VCVTDQ2PD zmm, ymm EVEX.512 -mavx512f

_mm512_cvtepi32lo_pd __m512d _mm512_cvtepi32lo_pd(__m512i __A)

VCVTDQ2PD zmm, ymm EVEX.512 -mavx512f

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

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

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

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

_mm512_maskz_cvtepi32_pd __m512d _mm512_maskz_cvtepi32_pd(__mmask8 __U, __m256i __A)

VCVTDQ2PD 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
AVX

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
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 AVX instructions

All 253 AVX instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-208 (CVTDQ2PD)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. 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 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.