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

VSUBPD subtracts the doubles of its last operand from those of the one before, two to an xmm register, four to a ymm one and eight to a zmm one. It is SUBPD in VEX and EVEX encodings: VSUBPS covers the order of the operands, the sign of a zero difference and what compilers make of a minus sign, and VADDPD what the encodings add for doubles, down to a broadcast of one 64-bit element. AMD’s Zen 5 guide lists it as it lists VSUBPS: one macro-op on the pipes FP2 and FP3, with a latency of 2 cycles.

Edges recorded on Zen 5

  • With MXCSR rounding down, vsubpd xmm12, xmm6, xmm6 turned 2 - 2 and 0.5 - 0.5 into -0.
  • Rounding toward zero, 0.1 broadcast from memory and subtracted from 10^300 gave the double just below 10^300, and subtracted from 10^-300 gave -0.09999999999999999 instead of -0.1. With DAZ set, a denormal minus 0.1 was exactly -0.1.
  • The largest denormal minus the smallest normal is -2^-1074, exact and itself a denormal: it came back as such, with DE set for the denormal input but not UE, since nothing was rounded.
  • With the denormal exception unmasked, {rn-sae} let a denormal minus itself give +0 without a #XM.
  • An element that the write mask leaves out raises nothing: with k1 selecting none of the four, vsubpd ymm24{k1}, ymm3, ymmword ptr [mem] met a signaling NaN, left IE clear and kept the destination’s old elements.

In compiled code

GCC 14 and Clang 23 at -O2 with -march=x86-64-v3 make b[i] - c[i] over doubles one VSUBPD per four elements, and 1.0 - b[i] one with the broadcast 1 as the first source. Two other shapes avoid it:

  • b[i] * c[i] - d[i] becomes a fused multiply-subtract, VFMSUB132PD in GCC and VFMSUB213PD in Clang, rounded once. GCC keeps VMULPD and VSUBPD under -std=c17, which turns contraction off; Clang contracts either way.
  • A loop that subtracts in its even elements and adds in its odd ones becomes VADDSUBPD in both.

In the optimization guide

What the optimization guide says about VSUBPD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Out of order

Forms

Every encoding of VSUBPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VSUBPD xmm, xmm, m128 VSUBPD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG 5C /rAVX
VSUBPD xmm, xmm, xmm VSUBPD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG 5C /rAVX
VSUBPD ymm, ymm, m256 VSUBPD_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG 5C /rAVX
VSUBPD ymm, ymm, ymm VSUBPD_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG 5C /rAVX
VSUBPD zmm {k}{z}, zmm, zmm, {er} VSUBPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F.W1 5C /rAVX10.1 or AVX512F
VSUBPD zmm {k}{z}, zmm, m512/m64bcst VSUBPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F.W1 5C /rAVX10.1 or AVX512F
VSUBPD xmm {k}{z}, xmm, xmm VSUBPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F.W1 5C /rAVX10.1 or AVX512F + AVX512VL
VSUBPD xmm {k}{z}, xmm, m128/m64bcst VSUBPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F.W1 5C /rAVX10.1 or AVX512F + AVX512VL
VSUBPD ymm {k}{z}, ymm, ymm VSUBPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F.W1 5C /rAVX10.1 or AVX512F + AVX512VL
VSUBPD ymm {k}{z}, ymm, m256/m64bcst VSUBPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F.W1 5C /rAVX10.1 or AVX512F + AVX512VL

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, m128
xmm {k}{z}, xmm, m128/m64bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmmno mask, with a mask
ymm {k}{z}, ymm, ymmno mask, with a mask
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m64bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmm, {er}no mask, with {er}zmm {k}{z}, zmm, zmm, {er}with a mask, zeroingzmm {k}{z}, zmm, m512/m64bcstxmm {k}{z}, xmm, xmmzeroing
ymm {k}{z}, ymm, ymmzeroing
Sandy Bridge, Haswell9 / 1p13 / 1p110 / 1p13 / 1p1
Broadwell8 / 1p13 / 1p19 / 1p13 / 1p1
Skylake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p01
Skylake-SP10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 0.5p054 / 0.5p0511 / 0.5p054 / 0.5p01
Ice Lake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 1p04 / 1p011 / 1p04 / 0.5p01
Alder Lake10 / 0.5p153 / 0.5p1511 / 0.5p153 / 0.5p15
Sapphire Rapids10 / 0.5p153 / 0.5p1511 / 0.5p153 / 0.5p153 / 0.5p054 / 0.5p0511 / 0.5p054 / 0.5p15
Lunar Lake10 / 0.5V2 V33 / 0.5V2 V311 / 0.5V2 V33 / 0.5V2 V3
Piledriver10 / 1.5FPFMA FPU05 / 1FPFMA FPU010 / 1.5FPFMA FPU05 / 1FPFMA FPU0
Zen10 / 0.5FPU2 FPU33 / 0.5FPU2 FPU310 / 1FPU2 FPU33 / 1FPU2 FPU3
Zen 210 / 0.5FPU2 FPU33 / 0.5FPU2 FPU310 / 0.5FPU2 FPU33 / 0.5FPU2 FPU3
Zen 310 / 0.5FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP33 / 0.5FP2 FP3
Zen 410 / 0.5FP2 FP33 / 0.5FP2 FP310 / 0.5FP2 FP33 / 0.5FP2 FP33 / 1FP2 FP33 / 1FP2 FP310 / 1FP2 FP33 / 0.5FP2 FP3
Jaguar8 / 1FPA FPU03 / 1FPA FPU08 / 2FPA FPU03 / 2FPA 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.

Element-wise: each double of the result comes from the double in the same place in each source.
VSUBPD: element by elementResult double i comes from double i of xmm2 and xmm3. Result doubles 1 to 0: a1-b1, a0-b0.01xmm2a11k1a0-b0a1-b1xmm101xmm3or m128b

Every double works alike: 2, 4 and 8 doubles in the xmm, ymm and zmm forms. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m64bcst, one double from memory stands for every element of the last source.

Result double i comes from double i of xmm2 and xmm3. Result doubles 1 to 0: a1-b1, a0-b0.

Operation

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

for i in range(VL // 64):
    if k1[i]:  # 1 without a write mask
        a = zmm2.f64[i]
        b = src3.f64[i]
        zmm1.f64[i] = sub(a, b)
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[i] keeps its value
# m64bcst: src3.f64[i] is the m64 for every i
# {er}: the form's rounding, not MXCSR.RC, and no flags
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 15 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
VSUBPD xmm, xmm, xmm/m128 VSUBPD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VSUBPD xmm {k}{z}, xmm, xmm/m128/m64bcst VSUBPD ymm {k}{z}, ymm, ymm/m256/m64bcst VSUBPD zmm {k}{z}, zmm, zmm/m512/m64bcst, {er}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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-2
EVEX forms
AVX512-E2

Attributes

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

All forms
follows MXCSR
EVEX forms
write masking
EVEX memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VSUBPD, 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_pd __m128d _mm_sub_pd(__m128d __a, __m128d __b)

VSUBPD xmm, xmm, xmm VEX.128 -mavxwith AVX enabled

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

VSUBPD xmm {k}, xmm, xmm EVEX.128 -mavx512vl

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

VSUBPD xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl

_mm256_sub_pd __m256d _mm256_sub_pd(__m256d __a, __m256d __b)

VSUBPD ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_sub_pd __m256d _mm256_mask_sub_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256d __B)

VSUBPD ymm {k}, ymm, ymm EVEX.256 -mavx512vl

_mm256_maskz_sub_pd __m256d _mm256_maskz_sub_pd(__mmask8 __U, __m256d __A, __m256d __B)

VSUBPD ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl

_mm512_sub_pd __m512d _mm512_sub_pd(__m512d __a, __m512d __b)

VSUBPD zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_sub_round_pd __m512d _mm512_sub_round_pd(__m512d A, __m512d B, const int R)

VSUBPD zmm, zmm, zmm, {er} EVEX.512 -mavx512f

_mm512_mask_sub_pd __m512d _mm512_mask_sub_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512d __B)

VSUBPD zmm {k}, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_sub_round_pd __m512d _mm512_mask_sub_round_pd(__m512d W, __mmask8 U, __m512d A, __m512d B, const int R)

VSUBPD zmm {k}, zmm, zmm, {er} EVEX.512 -mavx512f

_mm512_maskz_sub_pd __m512d _mm512_maskz_sub_pd(__mmask8 __U, __m512d __A, __m512d __B)

VSUBPD zmm {k}{z}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_sub_round_pd __m512d _mm512_maskz_sub_round_pd(__mmask8 U, __m512d A, __m512d B, const int R)

VSUBPD zmm {k}{z}, zmm, zmm, {er} EVEX.512 -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.
ISA setCPUIDProcessors
AVX

AVX
CPUID.01H:ECX[28] AVX

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, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX512F_512

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512F_128

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Cannon Lake, Ice Lake (client), Tiger Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512F_256
Same as AVX512F_128Same as AVX512F_128

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-687 (SUBPD)
  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.