Instruction
ROUNDSD
Rounds the low double of the source to an integral value, by an immediate or MXCSR; the upper half is kept.
- Extensions
- Forms
- 2 (2 Legacy)
- Data
- Intel XED v2026.08.23
ROUNDSD rounds the low double of its source to a whole number, still a double, and keeps bits 127:64 of the destination. Its immediate works as ROUNDPS describes: a direction in bits 1:0, MXCSR’s direction instead when bit 2 is set, and no precision exception when bit 3 is set. On Zen 5, rounding a tiny positive double up under 0Ah gave 1.0 and left both MXCSR and the upper double alone.
What C’s floor becomes
With -msse4.1, GCC 14 and Clang 23 at -O2 compile floor(x) to
roundsd xmm0, xmm0, 9, ceil to 0Ah and trunc to 0Bh, and
(long)floor(x) to ROUNDSD followed by
CVTTSD2SI. round(x), which rounds halves away from
zero, is a library call in GCC; Clang adds 0.49999999999999994 with the
sign of x and truncates. The intrinsics differ from the C functions in
one bit: _mm_floor_sd(a, b) compiles to roundsd xmm0, xmm1, 1,
since _MM_FROUND_FLOOR leaves the precision exception enabled, while
floor uses 9.
The upper half
The legacy form merges its result into the old destination, so the
instruction depends on whatever last wrote that register even when the
program only wants a scalar. Both compilers read floor(*p) with a
MOVSD load, which zeroes the upper half, and round in
place rather than use the memory form; for round(x) Clang zeroes the
destination with XORPS before rounding into it from another register.
AMD’s guide for Zen 5 names ROUNDSS and ROUNDSD among the instructions
that skip the wait for the old destination when its upper bits are
known to be zero (Section 2.11.5).
VROUNDSD, the VEX form, takes the upper double from a
separate register and clears the bits above 127. With -mavx, GCC
folds the load of floor(*p) into vroundsd xmm0, xmm0, qword ptr [rdi], 9, which takes the upper half from XMM0’s old contents; Clang
still loads with MOVSD first. AVX-512 has no EVEX form; it rounds with
VRNDSCALESD. ROUNDSS is the
single-precision form and ROUNDPD the packed one,
which Clang uses for a loop over floor and GCC, under its default
-ftrapping-math, does not.
Forms
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.
Result double 0 is computed from double 0 of xmm2; double 1 is that of xmm1. 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] = round(src2.f64[0], imm8)
# xmm1.q[1] keeps its value
# imm8[1:0]: rn, rd, ru, rz; bit 2: MXCSR.RC; bit 3: no PE
# bits 128 and up of the register are unchangedRun on AMD Zen 5 (EPYC 9645): 2 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
ROUNDSD xmm, xmm/m64, imm8 | ||
xmm | explicit | read, write |
xmm/m64 | explicit | read |
imm8 | explicit | read |
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.
- All forms
SSE_TYPE_3
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 ROUNDSD, 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.
| Intrinsic | Compiles to |
|---|---|
_mm_ceil_sd
__m128d _mm_ceil_sd(__m128d X, __m128d Y) |
|
_mm_floor_sd
__m128d _mm_floor_sd(__m128d X, __m128d Y) |
|
_mm_round_sd
__m128d _mm_round_sd(__m128d X, __m128d Y, const int M) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
SSE4 | SSE4.1 | Penryn, Nehalem, Westmere, 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, Silvermont, Goldmont, Goldmont Plus, Tremont, Snow Ridge, Lakefield, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, K10 (Family 10h), Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6 Note: XED's AMD_K10 inherits everything from its Westmere chip, including SSSE3, SSE4.1, SSE4.2, AES-NI and PCLMULQDQ; GCC's -march=amdfam10 has none of them. |
More SSE4.1 instructions
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-588 (ROUNDSD)
- AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit and 256-Bit Media Instructions (26568, rev. 3.25, November 2021), Wayback Machine copy of AMD's PDF
- 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, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.