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

VADDPD adds doubles, two to an xmm register, four to a ymm one and eight to a zmm one. It is ADDPD in VEX and EVEX encodings, which add what VADDPS shows for singles: a separate destination, the bits above the result cleared, and in EVEX a write mask, a rounding mode given in the instruction and a broadcast, here of one 64-bit double. Rounding and the invalid sums work as on the ADDPS page, with a double’s 53-bit significand.

A double constant in float code

In C, 0.1 is a double, so a[i] = b[i] + 0.1 over arrays of floats is computed in double precision and rounded back. GCC 14 and Clang 23 at -O2 with -march=x86-64-v3 do just that: each eight floats are widened in two halves by VCVTPS2PD, added by two VADDPD and narrowed again by two VCVTPD2PS, where b[i] + 0.1f is one VADDPS taking its operand from memory. For arrays of doubles, both use VADDPD on ymm registers; with -march=x86-64-v4, GCC moves to zmm registers and Clang stays with ymm.

Flushing to zero

With MXCSR’s FTZ bit set and underflow masked, a result too small to be a normal double becomes a zero of its sign, and the underflow and precision flags are set (MULPS covers FTZ and DAZ). In a case recorded on Zen 5 with FTZ set and rounding toward +infinity, the smallest denormal, 2^-1074, added to itself gave +0 instead of 2^-1073, and so did -2^-1023 plus 2^-1022. The largest denormal plus the smallest normal, an exact normal sum, came back as it was, but set the denormal flag for its input, as DAZ was clear.

On Zen 5

AMD’s Zen 5 guide lists VADDPD exactly as VADDPS: one macro-op on the pipes FP2 and FP3, a latency of 2 cycles and two per cycle at every width. A vector of doubles costs what a vector of singles does, for half as many additions.

Forms

Every encoding of VADDPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VADDPD xmm, xmm, m128 VADDPD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG 58 /rAVX
VADDPD xmm, xmm, xmm VADDPD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG 58 /rAVX
VADDPD ymm, ymm, m256 VADDPD_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG 58 /rAVX
VADDPD ymm, ymm, ymm VADDPD_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG 58 /rAVX
VADDPD zmm {k}{z}, zmm, zmm, {er} VADDPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F.W1 58 /rAVX10.1 or AVX512F
VADDPD zmm {k}{z}, zmm, m512/m64bcst VADDPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F.W1 58 /rAVX10.1 or AVX512F
VADDPD xmm {k}{z}, xmm, xmm VADDPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F.W1 58 /rAVX10.1 or AVX512F + AVX512VL
VADDPD xmm {k}{z}, xmm, m128/m64bcst VADDPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F.W1 58 /rAVX10.1 or AVX512F + AVX512VL
VADDPD ymm {k}{z}, ymm, ymm VADDPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F.W1 58 /rAVX10.1 or AVX512F + AVX512VL
VADDPD ymm {k}{z}, ymm, m256/m64bcst VADDPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F.W1 58 /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.
VADDPD: 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] = add(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
VADDPD xmm, xmm, xmm/m128 VADDPD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VADDPD xmm {k}{z}, xmm, xmm/m128/m64bcst VADDPD ymm {k}{z}, ymm, ymm/m256/m64bcst VADDPD 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 VADDPD, 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_add_pd __m128d _mm_add_pd(__m128d __a, __m128d __b)

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

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

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

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

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

_mm256_add_pd __m256d _mm256_add_pd(__m256d __a, __m256d __b)

VADDPD ymm, ymm, ymm VEX.256 -mavx

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

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

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

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

_mm512_add_pd __m512d _mm512_add_pd(__m512d __a, __m512d __b)

VADDPD zmm, zmm, zmm EVEX.512 -mavx512f

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

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

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

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

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

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

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

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

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

VADDPD 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 2A, page 3-16 (ADDPD)
  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.