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

VCVTTSD2SI is the VEX and EVEX form of CVTTSD2SI: the low double of an XMM register or of eight bytes of memory, truncated toward zero to a signed 32-bit or 64-bit integer in a general-purpose register. CVTTSD2SI’s page covers the cases that matter for doubles, and VCVTTSS2SI what the encodings change: VEX.vvvv and EVEX.vvvv must be 1111b, the EVEX form (AVX-512F or AVX10.1) reaches XMM16 to XMM31 and takes {sae} but no rounding mode, and the VEX form needs AVX.

Recorded on Zen 5

  • Under MXCSR 3FC0h, rounding down, vcvttsd2si ecx, xmm12 truncated 2,147,483,647.5 to 7FFFFFFFh and set PE: the largest result the 32-bit form can give, from a double that a single could not hold.
  • {evex} vcvttsd2si r14d, xmm5, {sae} gave 80000000h for 2^31, which does not fit, with the invalid exception unmasked (MXCSR 1E40h) and no #XM: MXCSR stayed as it was.
  • With FTZ and DAZ set (FFC0h), the smallest normal double, 2^-1022, from memory gave 0 and set PE; DAZ turns only denormal inputs into zeros.
  • A signaling NaN gave 8000000000000000h in the 64-bit form and set IE.

In compiled code

In our builds at -O2 with -march=x86-64-v3, testing whether a double holds an integer, x == (int)x, separates the compilers. GCC 14 keeps the round trip: VCVTTSD2SI, then VXORPS and VCVTSI2SD back, then VUCOMISD. Clang 23 drops the conversion and truncates in a vector register with vroundsd xmm1, xmm0, xmm0, 0xb before a VCMPEQSD, which at -v4 writes K0. An array of doubles truncated to long is one VCVTTSD2SI per element from memory at -v3 and the packed VCVTTPD2QQ at -v4, where (unsigned)x also becomes VCVTTSD2USI.

AMD’s latency spreadsheet for Zen 5 gives the VEX and EVEX rows two macro-ops each, and a latency of 4 cycles only in the EVEX row.

Forms

Every encoding of VCVTTSD2SI that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTTSD2SI r32, m64 VCVTTSD2SI_GPR32d_MEMqVEX.LIG.F2.0F.W0 2C /rAVX
VCVTTSD2SI r32, xmm VCVTTSD2SI_GPR32d_XMMqVEX.LIG.F2.0F.W0 2C /rAVX
VCVTTSD2SI r64, m64 64-bit mode only VCVTTSD2SI_GPR64q_MEMqVEX.LIG.F2.0F.W1 2C /rAVX
VCVTTSD2SI r64, xmm 64-bit mode only VCVTTSD2SI_GPR64q_XMMqVEX.LIG.F2.0F.W1 2C /rAVX
VCVTTSD2SI r32, xmm, {sae} VCVTTSD2SI_GPR32i32_XMMf64_AVX512EVEX.LIG.F2.0F.W0 2C /rAVX10.1 or AVX512F
VCVTTSD2SI r32, m64 VCVTTSD2SI_GPR32i32_MEMf64_AVX512EVEX.LIG.F2.0F.W0 2C /rAVX10.1 or AVX512F
VCVTTSD2SI r64, xmm, {sae} 64-bit mode only VCVTTSD2SI_GPR64i64_XMMf64_AVX512EVEX.LIG.F2.0F.W1 2C /rAVX10.1 or AVX512F
VCVTTSD2SI r64, m64 64-bit mode only VCVTTSD2SI_GPR64i64_MEMf64_AVX512EVEX.LIG.F2.0F.W1 2C /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.
Modelr32, m64r32, xmm
r64, xmm
r64, m64r32, xmm, {sae}
r64, xmm, {sae}
r32, m64r64, m64
Sandy Bridge10 / 1p015 / 1p0110 / 1p01
Haswell, Broadwell9 / 1p014 / 1p019 / 1p01
Skylake11 / 1p016 / 1p0111 / 1p01
Skylake-SP, Ice Lake11 / 1p016 / 1p0111 / 1p016 / 1p0111 / 1p0111 / 1p01
Alder Lake26 / 1p017 / 1p0112 / 1p01
Sapphire Rapids26 / 1p017 / 1p0112 / 1p017 / 1p0126 / 1p0112 / 1p01
Lunar Lake11 / 3.5V0 V17 / 3.5V0 V111 / 3.5V0 V1
Piledriver18 / 1.5EX0 FPCVT FPFMA FPU013 / 1EX0 FPCVT FPFMA FPSTO FPU018 / 1.5EX0 FPCVT FPFMA FPU0
Zen12 / 1FPU2 FPU35 / 1FPU2 FPU312 / 1FPU2 FPU3
Zen 211 / 1FPU2 FPU34 / 1FPU2 FPU311 / 1FPU2 FPU3
Zen 39 / 1FP2 FP32 / 1FP2 FP39 / 1FP2 FP3
Zen 412 / 2.5FP2 FP35 / 2.5FP2 FP312 / 2.5FP2 FP31 / 0.5FP2 FP38 / 0.5FP2 FP38 / 0.5FP2 FP3
Jaguar12 / 1ALU0 FPA FPU0 FPU17 / 1ALU0 FPA FPU0 FPU1 STC12 / 1ALU0 FPA FPU0 FPU1

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.

The low double of xmm2 is converted, and the integer goes to r32.
VCVTTSD2SI: the low element to r32r32 receives the conversion of double 0 of xmm2: r0.01xmm2ar0r32

r32 receives the conversion of double 0 of xmm2: r0.

Operation

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

a = src2.f64[0]
dest.write(cvtt_int(a, dest.bits))  # r32: bits 63:32 cleared
# {sae}: no exception flags

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
VCVTTSD2SI r32, xmm/m64 VCVTTSD2SI r64, xmm/m64 64-bit mode only VCVTTSD2SI r32, xmm/m64, {sae} VCVTTSD2SI r64, xmm/m64, {sae} 64-bit mode only
r32/64explicitwrite
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-E3NF

Attributes

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

All forms
follows MXCSR

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VCVTTSD2SI, 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_cvtt_roundsd_i32 int _mm_cvtt_roundsd_i32(__m128d A, const int R)

VCVTTSD2SI r32, xmm, {sae} EVEX.LIG -mavx512f

_mm_cvtt_roundsd_i64 long long _mm_cvtt_roundsd_i64(__m128d A, const int R)

VCVTTSD2SI r64, xmm, {sae} EVEX.LIG -mavx512f

_mm_cvtt_roundsd_si32 int _mm_cvtt_roundsd_si32(__m128d A, const int R)

VCVTTSD2SI r32, xmm, {sae} EVEX.LIG -mavx512f

_mm_cvtt_roundsd_si64 long long _mm_cvtt_roundsd_si64(__m128d A, const int R)

VCVTTSD2SI r64, xmm, {sae} EVEX.LIG -mavx512f

_mm_cvttsd_i32 int _mm_cvttsd_i32(__m128d __A)

VCVTTSD2SI r32, xmm VEX.LIG -mavx512f

_mm_cvttsd_i64 long long _mm_cvttsd_i64(__m128d __A)

VCVTTSD2SI r64, xmm VEX.LIG -mavx512f

_mm_cvttsd_si32 int _mm_cvttsd_si32(__m128d __a)

VCVTTSD2SI r32, xmm VEX.LIG -mavxwith AVX enabled

_mm_cvttsd_si64 long long _mm_cvttsd_si64(__m128d __a)

VCVTTSD2SI r64, xmm 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-253 (CVTTSD2SI)
  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.