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

VCVTPS2PD widens singles to doubles, 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. CVTPS2PD explains why the conversion cannot round, why each instruction reads only half a register’s worth of singles, and how GCC and Clang arrange the halves of an array. What the VEX and EVEX forms add:

  • Masks per double. Each mask bit selects one result double, so a zmm destination takes eight bits. On Zen 5, vcvtps2pd zmm14{k5}, ymm8, {sae} with E1H in the low byte of K5 converted elements 0, 5, 6 and 7 and left the others as they were.
  • A broadcast single. dword bcst widens one single into every element.
  • {sae} without rounding. A widening conversion is always exact, so the EVEX register form takes only {sae}, which silences the two exceptions it can raise: invalid for a signaling NaN and denormal for a denormal input. In that case, with MXCSR 1E40H (invalid and denormal unmasked), the signaling NaN 7F812345H became a quiet NaN, with no fault and no flag.

What becomes of a NaN

The single’s payload moves to the top of the double’s: Zen 5 widened 7FC12345H to 7FF82468A0000000H, the 23-bit fraction shifted up by 29 places, and the signaling 7F812345H to the same quiet value, setting IE where {sae} was absent. VCVTPD2PS narrows the other way and drops the low 29 bits.

Denormal inputs

Every single denormal is a normal double. With DAZ clear, Zen 5 widened -2^-127 (80400000H) to the double -2^-127 and set the denormal flag; with DAZ set, the same input gave -0.

In our builds at -O2, Clang 23 widens straight from memory, to ymm registers for -march=x86-64-v3 and x86-64-v4 and to zmm for znver5; GCC 14 loads a whole vector and splits it, with VEXTRACTF128 for x86-64-v3 and VEXTRACTF32X8 on zmm registers for x86-64-v4.

In the optimization guide

What the optimization guide says about VCVTPS2PD, 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 VCVTPS2PD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTPS2PD xmm, m64 VCVTPS2PD_XMMdq_MEMqVEX.128.NP.0F.WIG 5A /rAVX
VCVTPS2PD xmm, xmm VCVTPS2PD_XMMdq_XMMqVEX.128.NP.0F.WIG 5A /rAVX
VCVTPS2PD ymm, m128 VCVTPS2PD_YMMqq_MEMdqVEX.256.NP.0F.WIG 5A /rAVX
VCVTPS2PD ymm, xmm VCVTPS2PD_YMMqq_XMMdqVEX.256.NP.0F.WIG 5A /rAVX
VCVTPS2PD zmm {k}{z}, ymm, {sae} VCVTPS2PD_ZMMf64_MASKmskw_YMMf32_AVX512EVEX.512.NP.0F.W0 5A /rAVX10.1 or AVX512F
VCVTPS2PD zmm {k}{z}, m256/m32bcst VCVTPS2PD_ZMMf64_MASKmskw_MEMf32_AVX512EVEX.512.NP.0F.W0 5A /rAVX10.1 or AVX512F
VCVTPS2PD xmm {k}{z}, xmm VCVTPS2PD_XMMf64_MASKmskw_XMMf32_AVX512EVEX.128.NP.0F.W0 5A /rAVX10.1 or AVX512F + AVX512VL
VCVTPS2PD xmm {k}{z}, m64/m32bcst VCVTPS2PD_XMMf64_MASKmskw_MEMf32_AVX512EVEX.128.NP.0F.W0 5A /rAVX10.1 or AVX512F + AVX512VL
VCVTPS2PD ymm {k}{z}, xmm VCVTPS2PD_YMMf64_MASKmskw_XMMf32_AVX512EVEX.256.NP.0F.W0 5A /rAVX10.1 or AVX512F + AVX512VL
VCVTPS2PD ymm {k}{z}, m128/m32bcst VCVTPS2PD_YMMf64_MASKmskw_MEMf32_AVX512EVEX.256.NP.0F.W0 5A /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, xmm
xmm {k}{z}, xmm
ymm, m128
ymm {k}{z}, m128/m32bcst
ymm, xmm
ymm {k}{z}, xmm
zmm {k}{z}, ymm, {sae}no maskzmm {k}{z}, ymm, {sae}with a mask, zeroing, with {sae}zmm {k}{z}, m256/m32bcstxmm {k}{z}, m64/m32bcst
Sandy Bridge7 / 1p02 / 1p057 / 1p052 / 1p05
Haswell6 / 1p02 / 1p0510 / 1p04 / 1p05
Broadwell6 / 1p02 / 1p059 / 1p04 / 1p05
Skylake9 / 0.5p015 / 1p01511 / 0.5p017 / 1p015
Skylake-SP, Ice Lake9 / 0.5p015 / 1p01511 / 0.5p017 / 1p0157 / 1p053 / 1p0511 / 0.5p0110 / 0.5p01
Alder Lake11 / 0.5p015 / 1p01512 / 0.5p017 / 1p015
Sapphire Rapids11 / 0.5p015 / 1p01512 / 0.5p017 / 1p0157 / 1p057 / 1p0513 / 1p0511 / 0.5p01
Lunar Lake10 / 2V0 V15 / 2V0 V1 V2 V311 / 2.33V0 V17 / 2V0 V1 V2 V3
Piledriver13 / 1.5FPCVT FPU08 / 1FPCVT FPSTO FPU013 / 2FPCVT FPU08 / 2FPCVT FPSTO FPU0
Zen, Zen 210 / 1FPU33 / 1FPU310 / 1FPU33 / 1FPU3
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP311 / 1FP2 FP34 / 1FP2 FP3
Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP311 / 1FP2 FP34 / 1FP2 FP36 / 2FP2 FP36 / 2FP2 FP313 / 2FP2 FP310 / 0.5FP2 FP3
Jaguar7 / 1FPU12 / 1FPU1 STC7 / 2FPU12 / 2FPU1 STC

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 double, converted, in the same order.
VCVTPS2PD: 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 singles. 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.f32[i])
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[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): 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
VCVTPS2PD xmm, xmm/m64 VCVTPS2PD ymm, xmm/m128
xmm, ymmexplicitwrite
xmm/m64/128explicitread
VCVTPS2PD xmm {k}{z}, xmm/m64/m32bcst VCVTPS2PD ymm {k}{z}, xmm/m128/m32bcst VCVTPS2PD 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.

VEX forms
avx-type-3
VCVTPS2PD zmm {k}{z}, ymm/m256/m32bcst, {sae}
AVX512-E3
VCVTPS2PD xmm {k}{z}, xmm/m64/m32bcst VCVTPS2PD ymm {k}{z}, xmm/m128/m32bcst
AVX512-E2

Attributes

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

All forms
follows MXCSR
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 VCVTPS2PD, 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_cvtps_pd __m128d _mm_cvtps_pd(__m128 __a)

VCVTPS2PD xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_cvtps_pd __m128d _mm_mask_cvtps_pd(__m128d __W, __mmask8 __U, __m128 __A)

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

_mm_maskz_cvtps_pd __m128d _mm_maskz_cvtps_pd(__mmask8 __U, __m128 __A)

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

_mm256_cvtps_pd __m256d _mm256_cvtps_pd(__m128 __a)

VCVTPS2PD ymm, xmm VEX.256 -mavx

_mm256_mask_cvtps_pd __m256d _mm256_mask_cvtps_pd(__m256d __W, __mmask8 __U, __m128 __A)

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

_mm256_maskz_cvtps_pd __m256d _mm256_maskz_cvtps_pd(__mmask8 __U, __m128 __A)

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

_mm512_cvt_roundps_pd __m512d _mm512_cvt_roundps_pd(__m256 A, const int R)

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

_mm512_cvtps_pd __m512d _mm512_cvtps_pd(__m256 __A)

VCVTPS2PD zmm, ymm EVEX.512 -mavx512f

_mm512_cvtpslo_pd __m512d _mm512_cvtpslo_pd(__m512 __A)

VCVTPS2PD zmm, ymm EVEX.512 -mavx512f

_mm512_mask_cvt_roundps_pd __m512d _mm512_mask_cvt_roundps_pd(__m512d W, __mmask8 U, __m256 A, const int R)

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

_mm512_mask_cvtps_pd __m512d _mm512_mask_cvtps_pd(__m512d __W, __mmask8 __U, __m256 __A)

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

_mm512_mask_cvtpslo_pd __m512d _mm512_mask_cvtpslo_pd(__m512d __W, __mmask8 __U, __m512 __A)

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

_mm512_maskz_cvt_roundps_pd __m512d _mm512_maskz_cvt_roundps_pd(__mmask8 U, __m256 A, const int R)

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

_mm512_maskz_cvtps_pd __m512d _mm512_maskz_cvtps_pd(__mmask8 __U, __m256 __A)

VCVTPS2PD 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-228 (CVTPS2PD)
  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)
  8. AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit, 256-Bit, and 512-Bit Media Instructions (26568, rev. 3.27, July 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.