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

VSUBSD is SUBSD in VEX and EVEX encodings: the low double of its last operand subtracted from that of the operand before it, with the high double copied from that first source and the bits above 127 cleared. VSUBSS shows how the separate destination saves the copy that 1.0 - x needs with SUBSD, and VADDSS what else the encodings change. The VEX form needs AVX, the EVEX form AVX-512F or AVX10.1.

The fractional part

The SUBSD page computes x - (long)x through a conversion to an integer and back. With SSE4.1’s rounding available, x - floor(x) is shorter: in our builds with -march=x86-64-v3, GCC 14 and Clang 23 at -O2 emit vroundsd xmm1, xmm0, xmm0, 9 and vsubsd xmm0, xmm0, xmm1. For x86-64-v4, GCC takes VRNDSCALESD for the rounding instead, as VROUNDSD explains; VSUBSD stays.

On Zen 5

  • vsubsd xmm12, xmm6, xmm6, under MXCSR 3FC0H, subtracted the signaling NaN FFF0000000000001H from itself and set IE. The result was that NaN quieted, FFF8000000000001H, which Intel’s Volume 1 gives for two signaling NaNs (Table 4-8).
  • The EVEX vsubsd xmm0{k7}, xmm31, xmm16, {rz-sae}, with bit 0 of K7 set, computed the most negative double minus 2: rounded toward zero, the most negative double again. MXCSR (6600H) left the precision exception unmasked, yet {sae} gave no #XM and no PE.
  • vsubsd xmm9{k2}{z}, xmm9, qword ptr [mem], with bit 0 of K2 set, computed 3 minus 0.1 under FFC0H (toward zero) as 2.9 (4007333333333333H) and set PE.

AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows 2 cycles on pipes FP2 and FP3, the figures of SUBSD.

Forms

Every encoding of VSUBSD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VSUBSD xmm, xmm, m64 VSUBSD_XMMdq_XMMdq_MEMqVEX.LIG.F2.0F.WIG 5C /rAVX
VSUBSD xmm, xmm, xmm VSUBSD_XMMdq_XMMdq_XMMqVEX.LIG.F2.0F.WIG 5C /rAVX
VSUBSD xmm {k}{z}, xmm, xmm, {er} VSUBSD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.LIG.F2.0F.W1 5C /rAVX10.1 or AVX512F
VSUBSD xmm {k}{z}, xmm, m64 VSUBSD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.LIG.F2.0F.W1 5C /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}no mask, with a mask, with {er}
xmm {k}{z}, xmm, xmm, {er}zeroing
Sandy Bridge9 / 1p13 / 1p1
Haswell, Broadwell8 / 1p13 / 1p1
Skylake9 / 0.5p014 / 0.5p01
Skylake-SP, Ice Lake9 / 0.5p014 / 0.5p014 / 0.5p01
Alder Lake10 / 0.5p153 / 0.5p15
Sapphire Rapids10 / 0.5p153 / 0.5p154 / 0.5p15
Lunar Lake10 / 0.5V2 V33 / 0.5V2 V3
Piledriver10 / 1.5FPFMA FPU05 / 1FPFMA FPU0
Zen, Zen 210 / 0.5FPU2 FPU33 / 0.5FPU2 FPU3
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP3
Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP33 / 0.5FP2 FP3
Jaguar8 / 1FPA FPU03 / 1FPA FPU0

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.
VSUBSD: the low elementResult double 0 is computed from double 0 of xmm2 and xmm3; double 1 is that of xmm2. Result doubles 1 to 0: a1, a0-b0.01xmm2a1k1a0-b0a1xmm101xmm3or m64b

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

Result double 0 is computed from double 0 of xmm2 and xmm3; double 1 is that of xmm2. Result doubles 1 to 0: a1, a0-b0.

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
    a = xmm2.f64[0]
    b = src3.f64[0]
    xmm1.f64[0] = sub(a, b)
elif zeroing:
    xmm1.f64[0] = 0
# else: xmm1.f64[0] keeps its value
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): 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
VSUBSD xmm, xmm, xmm/m64
xmmexplicitwrite
xmmexplicitread
xmm/m64explicitread
VSUBSD 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 VSUBSD, 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_sub_round_sd __m128d _mm_sub_round_sd(__m128d A, __m128d B, const int R)

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

_mm_sub_sd __m128d _mm_sub_sd(__m128d __a, __m128d __b)

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

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

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

_mm_mask_sub_sd __m128d _mm_mask_sub_sd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B)

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

_mm_maskz_sub_round_sd __m128d _mm_maskz_sub_round_sd(__mmask8 U, __m128d A, __m128d B, const int R)

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

_mm_maskz_sub_sd __m128d _mm_maskz_sub_sd(__mmask8 __U, __m128d __A, __m128d __B)

VSUBSD 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 2B, page 4-693 (SUBSD)
  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.