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

VCVTPD2PS narrows doubles to singles, rounded: a ymm register or 32 bytes into an xmm register with VEX, a zmm into a ymm with EVEX. CVTPD2PS covers what narrowing does to each value, the half-width result, the x and y suffixes AT&T syntax needs for memory operands, and how compilers join two results into one store. What the EVEX forms add is control over the rounding and the exceptions of each instruction.

Rounding given in the instruction

With a zmm source register, {rn-sae}, {rd-sae}, {ru-sae} or {rz-sae} replaces MXCSR’s rounding and reports no exception. The cases recorded on Zen 5 with {rd-sae}, MXCSR asking for the nearest:

  • 0.1 became 3DCCCCCCH, where rounding to nearest gives 3DCCCCCDH;
  • -2,147,483,649 became CF000001H, the single below -2^31;
  • 10^300 became 7F7FFFFFH, the largest single, as an overflow rounded down does not reach infinity, and 10^-300 became +0.

With {rz-sae}, -1.7 × 10^44 likewise gave the most negative finite single, FF7FFFFFH.

Nothing reported

With every exception unmasked (MXCSR 0) and {rn-sae}, Zen 5 converted signaling NaNs, the smallest double denormal and -1.1 × 10^-308 without a fault, and MXCSR stayed 0: the NaNs came back quiet, the tiny values as zeros of their sign. Without the rounding operand, the same instruction raised #XM for a signaling NaN.

A narrowed NaN keeps only the top of its payload: 7FF0000000012345H became 7FC00000H, the payload bits below the single’s 23 lost. VCVTPS2PD shows the widening side.

Masks per single

A write mask has a bit per result single, eight for a zmm source. In vcvtpd2ps ymm24{k4}, zmm3, {rd-sae}, K4’s low byte DDH left elements 1 and 5 of YMM24 as they were.

In our builds at -O2 for -march=znver5, Clang 23 converts arrays from memory zmm to ymm, while for x86-64-v3 and x86-64-v4 it stays with ymm to xmm.

Forms

Every encoding of VCVTPD2PS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTPD2PS xmm, m128 VCVTPD2PS_XMMdq_MEMdqVEX.128.66.0F.WIG 5A /rAVX
VCVTPD2PS xmm, xmm VCVTPD2PS_XMMdq_XMMdqVEX.128.66.0F.WIG 5A /rAVX
VCVTPD2PS xmm, m256 VCVTPD2PS_XMMdq_MEMqqVEX.256.66.0F.WIG 5A /rAVX
VCVTPD2PS xmm, ymm VCVTPD2PS_XMMdq_YMMqqVEX.256.66.0F.WIG 5A /rAVX
VCVTPD2PS ymm {k}{z}, zmm, {er} VCVTPD2PS_YMMf32_MASKmskw_ZMMf64_AVX512_VL512EVEX.512.66.0F.W1 5A /rAVX10.1 or AVX512F
VCVTPD2PS ymm {k}{z}, m512/m64bcst VCVTPD2PS_YMMf32_MASKmskw_MEMf64_AVX512_VL512EVEX.512.66.0F.W1 5A /rAVX10.1 or AVX512F
VCVTPD2PS xmm {k}{z}, xmm VCVTPD2PS_XMMf32_MASKmskw_XMMf64_AVX512_VL128EVEX.128.66.0F.W1 5A /rAVX10.1 or AVX512F + AVX512VL
VCVTPD2PS xmm {k}{z}, m128/m64bcst VCVTPD2PS_XMMf32_MASKmskw_MEMf64_AVX512_VL128EVEX.128.66.0F.W1 5A /rAVX10.1 or AVX512F + AVX512VL
VCVTPD2PS xmm {k}{z}, ymm VCVTPD2PS_XMMf32_MASKmskw_YMMf64_AVX512_VL256EVEX.256.66.0F.W1 5A /rAVX10.1 or AVX512F + AVX512VL
VCVTPD2PS xmm {k}{z}, m256/m64bcst VCVTPD2PS_XMMf32_MASKmskw_MEMf64_AVX512_VL256EVEX.256.66.0F.W1 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, m128
xmm {k}{z}, m128/m64bcst
xmm, xmm
xmm {k}{z}, xmm
xmm, m256
xmm {k}{z}, m256/m64bcst
xmm, ymm
xmm {k}{z}, ymm
ymm {k}{z}, zmm, {er}ymm {k}{z}, m512/m64bcst
Sandy Bridge10 / 1p154 / 1p1511 / 1p154 / 1p15
Haswell10 / 1p154 / 1p1512 / 1p156 / 1p15
Broadwell9 / 1p154 / 1p1512 / 1p156 / 1p15
Skylake11 / 1p0155 / 1p01513 / 1p0157 / 1p015
Skylake-SP9 / 1p0155 / 1p01514 / 1p0157 / 1p0157 / 1p0514 / 1p05
Ice Lake11 / 1p0155 / 1p01514 / 1p0157 / 1p0157 / 1p0514 / 1p05
Alder Lake12 / 1p0155 / 1p01515 / 1p0157 / 1p015
Sapphire Rapids12 / 1p0155 / 1p01515 / 1p0157 / 1p0157 / 1p0515 / 1p05
Lunar Lake12 / 0.5V0 V1 V2 V35 / 0.5V0 V1 V2 V315 / 0.5V0 V1 V2 V37 / 0.5V0 V1 V2 V3
Piledriver13 / 1.5FPCVT FPU08 / 1FPCVT FPSTO FPU013 / 2FPCVT FPFMA FPU08 / 2FPCVT FPFMA FPSTO FPU0
Zen11 / 1FPU34 / 1FPU311 / 2FPU35 / 2FPU3
Zen 210 / 1FPU33 / 1FPU310 / 1FPU33 / 1FPU3
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP313 / 1FP2 FP36 / 1FP2 FP3
Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP313 / 1FP2 FP36 / 1FP2 FP36 / 21FP2 FP313 / 2FP2 FP3
Jaguar8 / 1FPU13 / 1FPU1 STC11 / 2FPA FPM FPU16 / 2FPA FPM FPU1 STC
  1. Zen 4 model: AMD's spreadsheets give latency 7 for Zen 4 and Zen 5 (AMD 57647, row 990; AMD 58455, row 56).

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 single, in the same order, at the low end of the result.
VCVTPD2PS: each element narrowedResult singles 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 EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.

Result singles 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
        ymm1.f32[i] = to_f32(src2.f64[i])
    elif zeroing:
        ymm1.f32[i] = 0
    # else: ymm1.f32[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
# {er}: the form's rounding, not MXCSR.RC, and no flags
# ymm1 is zeroed from bit 128 (xmm) or 256 (ymm) up

Run on AMD Zen 5 (EPYC 9645): 48 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
VCVTPD2PS xmm, xmm/m128 VCVTPD2PS xmm, ymm/m256
xmmexplicitwrite
xmm/m128, ymm/m256explicitread
VCVTPD2PS xmm {k}{z}, xmm/m128/m64bcst VCVTPD2PS xmm {k}{z}, ymm/m256/m64bcst VCVTPD2PS ymm {k}{z}, zmm/m512/m64bcst, {er}
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.

VEX forms
avx-type-2
EVEX forms
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 Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTPD2PS, 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_cvtpd_ps __m128 _mm_cvtpd_ps(__m128d __a)

VCVTPD2PS xmm, xmm VEX.128 -mavxwith AVX enabled

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

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

_mm_maskz_cvtpd_ps __m128 _mm_maskz_cvtpd_ps(__mmask8 __U, __m128d __A)

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

_mm256_cvtpd_ps __m128 _mm256_cvtpd_ps(__m256d __a)

VCVTPD2PS xmm, ymm VEX.256 -mavx

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

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

_mm256_maskz_cvtpd_ps __m128 _mm256_maskz_cvtpd_ps(__mmask8 __U, __m256d __A)

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

_mm512_cvt_roundpd_ps __m256 _mm512_cvt_roundpd_ps(__m512d A, const int R)

VCVTPD2PS ymm, zmm, {er} EVEX.512 -mavx512f

_mm512_cvtpd_ps __m256 _mm512_cvtpd_ps(__m512d __A)

VCVTPD2PS ymm, zmm EVEX.512 -mavx512f

_mm512_cvtpd_pslo __m512 _mm512_cvtpd_pslo(__m512d __A)

VCVTPD2PS ymm, zmm EVEX.512 -mavx512f

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

VCVTPD2PS ymm {k}, zmm, {er} EVEX.512 -mavx512f

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

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

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

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

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

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

_mm512_maskz_cvtpd_ps __m256 _mm512_maskz_cvtpd_ps(__mmask8 __U, __m512d __A)

VCVTPD2PS 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
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-219 (CVTPD2PS)
  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.