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

VCVTTSS2SI is CVTTSS2SI in VEX and EVEX encodings: the low single of an XMM register or of four bytes of memory, truncated toward zero to a signed integer in a 32-bit or 64-bit general-purpose register. CVTTSS2SI’s page covers the truncation, the integer indefinite value and the unsigned conversions. The destination is a general-purpose register, so the new encodings add no third operand and no zeroing of a vector register; VEX.vvvv and EVEX.vvvv must be 1111b. The VEX form needs AVX. The EVEX form, with AVX-512F or AVX10.1, can reach XMM16 to XMM31 and adds {sae}, which keeps IE and PE from being reported; it has no rounding mode, since the T fixes the rounding.

Recorded on Zen 5

  • vcvttss2si r9d, xmm8 truncated -2.5 to -2 (FFFFFFFEh in R9, the upper half cleared) under MXCSR 3FC0h, which asks for rounding down, and set PE.
  • {evex} vcvttss2si r14d, xmm17, {sae} truncated the same -2.5 to -2 and left MXCSR at 1E40h, without PE.
  • {evex} vcvttss2si r14, xmm0, {sae} turned 10^30 into the indefinite 8000000000000000h, and MXCSR 1E40h, whose invalid exception is unmasked, gave no #XM and no IE.
  • The 32-bit form gave 80000000h for 2^63 and set IE.

In compiled code

In our builds at -O2 with -march=x86-64-v3 or -v4, (int)x of a float is vcvttss2si eax, xmm0 and (long)x the form with RAX. An array of floats truncated to long stays scalar at -v3: GCC 14 converts each element from memory, Clang 23 also gathers pairs with VMOVQ and VPUNPCKLQDQ for wide stores. At -march=x86-64-v4 both use the packed VCVTTPS2QQ, and (unsigned)x becomes VCVTTSS2USI instead of the 64-bit conversion. _mm_cvtt_roundss_i32(a, _MM_FROUND_NO_EXC) gives the {sae} form.

AMD’s latency spreadsheet for Zen 5 gives two macro-ops on pipes FP2/3 and FP4/5 in both rows, and a latency of 4 cycles only in the EVEX row; the VEX row, like CVTTSS2SI’s, lists none.

Forms

Every encoding of VCVTTSS2SI that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VCVTTSS2SI r32, m32 VCVTTSS2SI_GPR32d_MEMdVEX.LIG.F3.0F.W0 2C /rAVX
VCVTTSS2SI r32, xmm VCVTTSS2SI_GPR32d_XMMdVEX.LIG.F3.0F.W0 2C /rAVX
VCVTTSS2SI r64, m32 64-bit mode only VCVTTSS2SI_GPR64q_MEMdVEX.LIG.F3.0F.W1 2C /rAVX
VCVTTSS2SI r64, xmm 64-bit mode only VCVTTSS2SI_GPR64q_XMMdVEX.LIG.F3.0F.W1 2C /rAVX
VCVTTSS2SI r32, xmm, {sae} VCVTTSS2SI_GPR32i32_XMMf32_AVX512EVEX.LIG.F3.0F.W0 2C /rAVX10.1 or AVX512F
VCVTTSS2SI r32, m32 VCVTTSS2SI_GPR32i32_MEMf32_AVX512EVEX.LIG.F3.0F.W0 2C /rAVX10.1 or AVX512F
VCVTTSS2SI r64, xmm, {sae} 64-bit mode only VCVTTSS2SI_GPR64i64_XMMf32_AVX512EVEX.LIG.F3.0F.W1 2C /rAVX10.1 or AVX512F
VCVTTSS2SI r64, m32 64-bit mode only VCVTTSS2SI_GPR64i64_MEMf32_AVX512EVEX.LIG.F3.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, m32
r64, m32
r32, xmm
r32, xmm, {sae}
r64, xmm
r64, xmm, {sae}
Sandy Bridge10 / 1p015 / 1p015 / 1p01
Haswell, Broadwell9 / 1p014 / 1p014 / 1p01
Skylake, Skylake-SP, Ice Lake11 / 1p016 / 1p017 / 1p015
Alder Lake, Sapphire Rapids12 / 1p017 / 1p018 / 1p015
Lunar Lake11 / 3.5V0 V17 / 3.5V0 V18 / 3.5V0 V1 V2 V3
Piledriver18 / 1.5EX0 FPCVT FPFMA FPU013 / 1EX0 FPCVT FPFMA FPSTO FPU013 / 1EX0 FPCVT FPFMA FPSTO FPU0
Zen12 / 1FPU1 FPU2 FPU35 / 1FPU1 FPU2 FPU35 / 1FPU1 FPU2 FPU3
Zen 210 / 1FPU1 FPU2 FPU33 / 1FPU1 FPU2 FPU33 / 1FPU1 FPU2 FPU3
Zen 39 / 1FP2 FP32 / 1FP2 FP32 / 1FP2 FP3
Zen 412 / 2.5FP2 FP35 / 2.5FP2 FP35 / 2.5FP2 FP3
Jaguar12 / 1ALU0 FPA FPU0 FPU17 / 1ALU0 FPA FPU0 FPU1 STC7 / 1ALU0 FPA FPU0 FPU1 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.

The low single of xmm2 is converted, and the integer goes to r32.
VCVTTSS2SI: the low element to r32r32 receives the conversion of single 0 of xmm2: r0.0123xmm2ar0r32

r32 receives the conversion of single 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.f32[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
VCVTTSS2SI r32, xmm/m32 VCVTTSS2SI r64, xmm/m32 64-bit mode only VCVTTSS2SI r32, xmm/m32, {sae} VCVTTSS2SI r64, xmm/m32, {sae} 64-bit mode only
r32/64explicitwrite
xmm/m32explicitread

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 VCVTTSS2SI, 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_roundss_i32 int _mm_cvtt_roundss_i32(__m128 A, const int R)

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

_mm_cvtt_roundss_i64 long long _mm_cvtt_roundss_i64(__m128 A, const int R)

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

_mm_cvtt_roundss_si32 int _mm_cvtt_roundss_si32(__m128 A, const int R)

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

_mm_cvtt_roundss_si64 long long _mm_cvtt_roundss_si64(__m128 A, const int R)

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

_mm_cvtt_ss2si int _mm_cvtt_ss2si(__m128 __a)

VCVTTSS2SI r32, xmm VEX.LIG -mavxwith AVX enabled

_mm_cvttss_i32 int _mm_cvttss_i32(__m128 __A)

VCVTTSS2SI r32, xmm VEX.LIG -mavx512f

_mm_cvttss_i64 long long _mm_cvttss_i64(__m128 __A)

VCVTTSS2SI r64, xmm VEX.LIG -mavx512f

_mm_cvttss_si32 int _mm_cvttss_si32(__m128 __a)

VCVTTSS2SI r32, xmm VEX.LIG -mavxwith AVX enabled

_mm_cvttss_si64 long long _mm_cvttss_si64(__m128 __a)

VCVTTSS2SI 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-255 (CVTTSS2SI)
  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.