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

VCVTSD2SS is the VEX and EVEX form of CVTSD2SS, whose page covers what narrowing a double does: rounding as MXCSR.RC says, overflow, underflow and the NaN payload, with cases recorded on Zen 5 for this VEX form. What the newer encodings add is the first source: the single goes into bits 31:0, bits 127:32 come from the first source, and the register is cleared above bit 127. VEX needs AVX. The EVEX form, with AVX-512F or AVX10.1, adds a write mask on the low single and, for a register source, a rounding mode of its own, {rn-sae}, {rd-sae}, {ru-sae} or {rz-sae}, which replaces MXCSR.RC for this one instruction and reports no exception.

One register in two roles

In the recorded vcvtsd2ss xmm7, xmm11, xmm7, XMM7 was both the double to narrow and the destination. Its low single became 7FC00000h, the quiet NaN that CVTSD2SS’s page shows for the signaling NaN 7FF0000000012345h, IE was set, and singles 1 to 3 came from XMM11: nothing of the old XMM7 above bit 31 survived.

In compiled code

In our builds at -O2 with -march=x86-64-v3 or -v4, (float)x of a double argument is vcvtsd2ss xmm0, xmm0, xmm0. A double read from a global array goes the two ways shown for VCVTSS2SD: GCC 14 zeroes XMM0 with VXORPS and converts from memory, Clang 23 loads with VMOVSD and converts register to register. Summing a double array into a float, GCC narrows four doubles at a time with VCVTPD2PS (eight at -v4) and adds the singles in order, while Clang stays scalar, narrowing each loaded register into itself. _mm_cvt_roundsd_ss(a, b, _MM_FROUND_TO_ZERO | _MM_FROUND_NO_EXC) gives vcvtsd2ss xmm0, xmm0, xmm1, {rz-sae} in both.

AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows alike one macro-op with a latency of 3 cycles on pipes FP2 and FP3, the figures of CVTSD2SS.

Forms

Every encoding of VCVTSD2SS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTSD2SS xmm, xmm, m64 VCVTSD2SS_XMMdq_XMMdq_MEMqVEX.LIG.F2.0F.WIG 5A /rAVX
VCVTSD2SS xmm, xmm, xmm VCVTSD2SS_XMMdq_XMMdq_XMMqVEX.LIG.F2.0F.WIG 5A /rAVX
VCVTSD2SS xmm {k}{z}, xmm, xmm, {er} VCVTSD2SS_XMMf32_MASKmskw_XMMf64_XMMf64_AVX512EVEX.LIG.F2.0F.W1 5A /rAVX10.1 or AVX512F
VCVTSD2SS xmm {k}{z}, xmm, m64 VCVTSD2SS_XMMf32_MASKmskw_XMMf64_MEMf64_AVX512EVEX.LIG.F2.0F.W1 5A /rAVX10.1 or AVX512F

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, xmm, m64
xmm {k}{z}, xmm, m64
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm, {er}
Sandy Bridge10 / 1p154 / 1p15
Haswell, Broadwell9 / 1p154 / 1p15
Skylake, Skylake-SP, Ice Lake10 / 1p0155 / 1p015
Alder Lake, Sapphire Rapids12 / 1p0155 / 1p015
Lunar Lake11 / 2V0 V1 V2 V35 / 0.5V0 V1 V2 V3
Piledriver9 / 2FPCVT FPU04 / 2FPCVT FPSTO FPU0
Zen11 / 1FPU34 / 1FPU3
Zen 210 / 1FPU33 / 1FPU3
Zen 3, Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP3
Jaguar12 / 2FPU17 / 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.

Scalar: only the low single is computed; the other singles come from xmm2.
VCVTSD2SS: the low elementResult single 0 is computed from double 0 of xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: a3, a2, a1, r0.0123xmm2a1k1r0a1a2a3xmm101xmm3or m64b

The write mask k1 applies to the low single: with bit 0 clear it keeps its old value, or is zeroed with {z}.

Result single 0 is computed from double 0 of xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: a3, a2, a1, r0.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

if k1[0]:  # 1 without a write mask
    xmm1.f32[0] = to_f32(src3.f64[0])
elif zeroing:
    xmm1.f32[0] = 0
# else: xmm1.f32[0] keeps its value
for i in range(1, 4):
    xmm1.d[i] = xmm2.d[i]
# {er}: the form's rounding, not MXCSR.RC, and no flags
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 6 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
VCVTSD2SS xmm, xmm, xmm/m64
xmmexplicitwrite
xmmexplicitread
xmm/m64explicitread
VCVTSD2SS xmm {k}{z}, xmm, xmm/m64, {er}
xmmexplicitwrite (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m64explicitread

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
EVEX forms
AVX512-E3

Attributes

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

All forms
follows MXCSR
EVEX forms
write masking
EVEX memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTSD2SS, 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_cvt_roundsd_ss __m128 _mm_cvt_roundsd_ss(__m128 A, __m128d B, const int R)

VCVTSD2SS xmm, xmm, xmm, {er} EVEX.LIG -mavx512f

_mm_cvtsd_ss __m128 _mm_cvtsd_ss(__m128 __a, __m128d __b)

VCVTSD2SS xmm, xmm, xmm VEX.LIG -mavxwith AVX enabled

_mm_mask_cvt_roundsd_ss __m128 _mm_mask_cvt_roundsd_ss(__m128 W, __mmask8 U, __m128 A, __m128d B, const int R)

VCVTSD2SS xmm {k}, xmm, xmm, {er} EVEX.LIG -mavx512f

_mm_mask_cvtsd_ss __m128 _mm_mask_cvtsd_ss(__m128 __W, __mmask8 __U, __m128 __A, __m128d __B)

VCVTSD2SS xmm {k}, xmm, xmm EVEX.LIG -mavx512f

_mm_maskz_cvt_roundsd_ss __m128 _mm_maskz_cvt_roundsd_ss(__mmask8 U, __m128 A, __m128d B, const int R)

VCVTSD2SS xmm {k}{z}, xmm, xmm, {er} EVEX.LIG -mavx512f

_mm_maskz_cvtsd_ss __m128 _mm_maskz_cvtsd_ss(__mmask8 __U, __m128 __A, __m128d __B)

VCVTSD2SS xmm {k}{z}, xmm, xmm EVEX.LIG -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.

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-234 (CVTSD2SS)
  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. 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.