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

VCVTSI2SD converts a signed 32-bit or 64-bit integer, from a general-purpose register or memory, to a double in bits 63:0, with bits 127:64 from the first source and the register cleared above bit 127. CVTSI2SD covers the conversion, the wait on the merged register that the VEX form’s separate source exists to avoid, and the registers GCC 14 and Clang 23 name there: one zeroed before a loop, or XMM15. The VEX form needs AVX; the EVEX form, with AVX-512F or AVX10.1, has no write mask and adds a rounding mode only to the 64-bit register form. Every 32-bit integer has an exact double, and Intel’s entry says a rounding operand on the 32-bit EVEX form is ignored.

Recorded on Zen 5

  • {evex} vcvtsi2sd xmm24, xmm3, r14, {rz-sae} turned R14 = 8000000000000001h, -(2^63 - 1), into -(2^63 - 1024), C3DFFFFFFFFFFFFFh. MXCSR was 6600h, with the precision exception unmasked, and nothing was raised or flagged.
  • The EVEX 64-bit memory form read 8008000000000000h, bytes that as a double would be a negative denormal, with DAZ set (FFC0h). As an integer it is -9,221,120,237,041,090,560, which converted exactly to C3DFFE0000000000h; DAZ applies to floating-point inputs only.
  • vcvtsi2sd xmm7, xmm11, r9d read only R9D, 80000001h, and gave -2,147,483,647.0, whatever the upper half of R9 held.

In compiled code

In our builds at -O2, (double)x of an int or long is the VEX form at -march=x86-64-v3 and still at -v4: GCC with a VXORPS of the destination first, Clang with XMM15 as the first source. At -v4 the other conversions change: an array of long becomes VCVTQQ2PD, eight or four at a time, and an unsigned int goes straight to VCVTUSI2SD, where -v3 zero-extends it and uses the 64-bit VCVTSI2SD. _mm_cvt_roundi64_sd(a, x, _MM_FROUND_TO_ZERO | _MM_FROUND_NO_EXC) gives vcvtsi2sd xmm0, xmm0, rdi, {rz-sae} in both.

AMD’s latency spreadsheet for Zen 5 lists the VEX and EVEX rows alike: two macro-ops from a register and one from memory, a latency of 3 cycles, the figures of VCVTSI2SS.

Forms

Every encoding of VCVTSI2SD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTSI2SD xmm, xmm, m32 VCVTSI2SD_XMMdq_XMMdq_MEMdVEX.LIG.F2.0F.W0 2A /rAVX
VCVTSI2SD xmm, xmm, r32 VCVTSI2SD_XMMdq_XMMdq_GPR32dVEX.LIG.F2.0F.W0 2A /rAVX
VCVTSI2SD xmm, xmm, m64 64-bit mode only VCVTSI2SD_XMMdq_XMMdq_MEMqVEX.LIG.F2.0F.W1 2A /rAVX
VCVTSI2SD xmm, xmm, r64 64-bit mode only VCVTSI2SD_XMMdq_XMMdq_GPR64qVEX.LIG.F2.0F.W1 2A /rAVX
VCVTSI2SD xmm, xmm, r32 VCVTSI2SD_XMMf64_XMMf64_GPR32i32_AVX512EVEX.LIG.F2.0F.W0 2A /rAVX10.1 or AVX512F
VCVTSI2SD xmm, xmm, m32 VCVTSI2SD_XMMf64_XMMf64_MEMi32_AVX512EVEX.LIG.F2.0F.W0 2A /rAVX10.1 or AVX512F
VCVTSI2SD xmm, xmm, r64, {er} 64-bit mode only VCVTSI2SD_XMMf64_XMMf64_GPR64i64_AVX512EVEX.LIG.F2.0F.W1 2A /rAVX10.1 or AVX512F
VCVTSI2SD xmm, xmm, m64 64-bit mode only VCVTSI2SD_XMMf64_XMMf64_MEMi64_AVX512EVEX.LIG.F2.0F.W1 2A /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, m32
xmm, xmm, m64
xmm, xmm, r32
xmm, xmm, r64
xmm, xmm, r64, {er}
Sandy Bridge, Haswell, Broadwell9 / 1p14 / 1p15
Skylake10 / 0.5p015 / 1p015
Skylake-SP, Ice Lake9 / 1p15 / 1p015
Alder Lake, Sapphire Rapids11 / 0.5p017 / 1p015
Lunar Lake10 / 2V0 V18 / 2V0 V1 p1 p3 p5
Piledriver9 / 1.5FPCVT FPU014 / 1FPCVT FPSTO FPU0
Zen12 / 1FPU35 / 1FPU0 FPU1 FPU3
Zen 212 / 1FPU33 / 1FPU0 FPU1 FPU3
Zen 310 / 1FP2 FP34 / 1FP2 FP3
Zen 411 / 1FP2 FP35 / 11FP2 FP3
Jaguar9 / 1FPU110 / 1FPU1 STC
  1. Zen 4 model: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 1043; AMD 58455, row 1064).

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 double is computed; the other double comes from xmm2.
VCVTSI2SD: the low elementResult double 0 is computed from r32; double 1 is that of xmm2. Result doubles 1 to 0: a1, r0.01xmm2ar0a1xmm10r32or r64, m32, m64b

Result double 0 is computed from r32; double 1 is that of xmm2. Result doubles 1 to 0: a1, r0.

Operation

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

xmm1.f64[0] = to_f64(signed(src3))
xmm1.q[1] = xmm2.q[1]
# {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): 12 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
VCVTSI2SD xmm, xmm, r/m32 VCVTSI2SD xmm, xmm, r/m64 64-bit mode only VCVTSI2SD xmm, xmm, r/m64, {er} 64-bit mode only
xmmexplicitwrite
xmmexplicitread
r/m32/64explicitread

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
VCVTSI2SD xmm, xmm, r/m32
AVX512-E10NF
VCVTSI2SD xmm, xmm, r/m64, {er} 64-bit mode only
AVX512-E3NF

Attributes

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

VCVTSI2SD xmm, xmm, r/m32 VCVTSI2SD xmm, xmm, r/m64 64-bit mode only VCVTSI2SD xmm, xmm, r/m64, {er} 64-bit mode only
follows MXCSR

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTSI2SD, 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_roundi64_sd __m128d _mm_cvt_roundi64_sd(__m128d A, long long B, const int R)

VCVTSI2SD xmm, xmm, r64, {er} EVEX.LIG -mavx512f

_mm_cvt_roundsi64_sd __m128d _mm_cvt_roundsi64_sd(__m128d A, long long B, const int R)

VCVTSI2SD xmm, xmm, r64, {er} EVEX.LIG -mavx512f

_mm_cvtsi32_sd __m128d _mm_cvtsi32_sd(__m128d __a, int __b)

VCVTSI2SD xmm, xmm, r32 VEX.LIG -mavxwith AVX enabled

_mm_cvtsi64_sd __m128d _mm_cvtsi64_sd(__m128d __a, long long __b)

VCVTSI2SD xmm, xmm, r64 VEX.LIG -mavxwith AVX enabled

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-236 (CVTSI2SD)
  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.