Instruction
VPADDD
Adds packed doublewords, wrapping around on overflow.
VPADDD is PADDD in VEX and EVEX encodings: it adds doublewords element by element and lets each sum wrap around, with no flags. The PADDD page covers the addition and its uses in compiled code, the vectorized sums and the all-ones constant among them. What the newer encodings add:
- A third operand.
vpaddd ymm0, ymm1, [mem]keeps both sources, and the memory operand may sit at any address, so a load folds into the addition where legacy SSE needs a separate MOVDQU. GCC 14 and Clang 23 at -O2 with-march=x86-64-v3compilea[i] = b[i] + c[i]over 1,024ints to one load, a VPADDD with a memory operand and a store per 32 bytes. - Clearing above the width. The VEX.128 form clears bits 128 and up of the destination, as every VEX and EVEX form does above its width.
- Masks and a broadcast operand. The EVEX forms (AVX512F, or
AVX10.1) add a write mask per doubleword, with merging or zeroing, and
can read a single doubleword from memory and add it to every element
(
{1to16}for a zmm register).
Broadcasts in practice
The compilers differ on the broadcast form. With -march=x86-64-v4,
Clang 23 compiles _mm512_add_epi32(x, _mm512_set1_epi32(5)) to vpaddd zmm0, zmm0, dword ptr [rip + c]{1to16}, reading the constant from a
4-byte pool entry, and a masked add of *p to vpaddd zmm0{k1}, zmm1, dword ptr [rsi]{1to16}. GCC 14 first loads the value into a whole
register with VPBROADCASTD and adds that. In a
loop both broadcast once before it, so the difference matters in
straight-line code.
That target also changes the width: GCC 14 vectorizes the loop above with zmm registers, 64 bytes at a time, while Clang 23 stays with ymm registers.
Zen 5’s 66 recorded cases cover every form: the VEX ones with a register
or memory source, and the EVEX ones unmasked, merging, zeroing and with
broadcast, including a destination that is also both sources (vpaddd zmm5{k3}, zmm5, zmm5).
In the optimization guide
What the optimization guide says about VPADDD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Zen 2
- Vectors and floating point: A float addition or multiplication takes three cycles and an FMA five, each on two pipes, and VPADDD one cycle on any of three; AMD’s spreadsheet, LLVM’s model and Agner Fog agree.
Zen 3
- Vectors and floating point: LLVM’s model gives a float addition or multiplication three cycles and an FMA four, each on two pipes, and VPADDD one cycle on any of the four.
Zen 4
- Vectors and floating point: LLVM’s model gives VPADDD a latency of one cycle on any of the four pipes, and VFMADD231PS four cycles on pipe 0 or 1; the 512-bit forms keep their pipe for two cycles, so they finish half as many per cycle.
Zen 5
- Vectors and floating point: AMD’s latency spreadsheet gives VPADDD a latency of one cycle and a throughput of four per cycle, on any of the four vector pipes. sources differ
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPADDD xmm, xmm, m128
VPADDD_XMMdq_XMMdq_MEMdq | VEX.128.66.0F.WIG FE /r | AVX |
VPADDD xmm, xmm, xmm
VPADDD_XMMdq_XMMdq_XMMdq | VEX.128.66.0F.WIG FE /r | AVX |
VPADDD ymm, ymm, m256
VPADDD_YMMqq_YMMqq_MEMqq | VEX.256.66.0F.WIG FE /r | AVX2 |
VPADDD ymm, ymm, ymm
VPADDD_YMMqq_YMMqq_YMMqq | VEX.256.66.0F.WIG FE /r | AVX2 |
VPADDD zmm {k}{z}, zmm, zmm
VPADDD_ZMMu32_MASKmskw_ZMMu32_ZMMu32_AVX512 | EVEX.512.66.0F.W0 FE /r | AVX10.1 or AVX512F |
VPADDD zmm {k}{z}, zmm, m512/m32bcst
VPADDD_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512 | EVEX.512.66.0F.W0 FE /r | AVX10.1 or AVX512F |
VPADDD xmm {k}{z}, xmm, xmm
VPADDD_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512 | EVEX.128.66.0F.W0 FE /r | AVX10.1 or AVX512F + AVX512VL |
VPADDD xmm {k}{z}, xmm, m128/m32bcst
VPADDD_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512 | EVEX.128.66.0F.W0 FE /r | AVX10.1 or AVX512F + AVX512VL |
VPADDD ymm {k}{z}, ymm, ymm
VPADDD_YMMu32_MASKmskw_YMMu32_YMMu32_AVX512 | EVEX.256.66.0F.W0 FE /r | AVX10.1 or AVX512F + AVX512VL |
VPADDD ymm {k}{z}, ymm, m256/m32bcst
VPADDD_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512 | EVEX.256.66.0F.W0 FE /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m32bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m32bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m32bcst |
|---|---|---|---|---|---|---|
| Sandy Bridge | 7 / 0.5p15 | 1 / 0.5p15 | ||||
| Haswell | 7 / 0.5p15 | 1 / 0.5p15 | 8 / 0.5p15 | 1 / 0.5p15 | ||
| Broadwell | 6 / 0.5p15 | 1 / 0.5p15 | 7 / 0.5p15 | 1 / 0.5p15 | ||
| Skylake | 7 / 0.5p015 | 1 / 0.33p015 | 8 / 0.5p015 | 1 / 0.33p015 | ||
| Skylake-SP, Ice Lake | 7 / 0.5p015 | 1 / 0.33p015 | 8 / 0.5p015 | 1 / 0.33p015 | 1 / 0.33p015 | 8 / 0.5p015 |
| Alder Lake | 8 / 0.33p015 | 1 / 0.33p015 | 9 / 0.33p015 | 1 / 0.33p015 | ||
| Sapphire Rapids | 8 / 0.33p015 | 1 / 0.33p015 | 9 / 0.33p015 | 1 / 0.33p015 | 1 / 0.5p05 | 9 / 0.5p05 |
| Lunar Lake | 7 / 2V0 V1 V2 V3 | 1 / 0.25V0 V1 V2 V3 | 8 / 2.33V0 V1 V2 V3 | 1 / 0.25V0 V1 V2 V3 | ||
| Piledriver | 7 / 1.5FPMAL | 2 / 0.5FPMAL FPU2 FPU3 | ||||
| Zen | 8 / 0.5FPU0 FPU1 FPU3 | 1 / 0.33FPU0 FPU1 FPU3 | 8 / 0.67FPU0 FPU1 FPU3 | 1 / 0.67FPU0 FPU1 FPU3 | ||
| Zen 2 | 8 / 0.33FPU0 FPU1 FPU3 | 1 / 0.33FPU0 FPU1 FPU3 | 8 / 0.33FPU0 FPU1 FPU3 | 1 / 0.33FPU0 FPU1 FPU3 | ||
| Zen 3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | ||
| Zen 4 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 1 / 0.5FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 |
| Jaguar | 6 / 1FPU0 FPU1 VALU0 VALU1 | 1 / 0.5FPU0 FPU1 VALU0 VALU1 | ||||
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.
Every doubleword works alike: 4, 8 and 16 doublewords 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 m32bcst, one doubleword from memory stands for every element of the last source.
Result doubleword i comes from doubleword i of xmm2 and xmm3. Result doublewords 3 to 0: a3+b3, unchanged (bit 2 of k1 is 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 // 32):
if k1[i]: # 1 without a write mask
zmm1.d[i] = zmm2.d[i] + src3.d[i]
elif zeroing:
zmm1.d[i] = 0
# else: zmm1.d[i] keeps its value
# m32bcst: src3.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 66 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPADDD xmm, xmm, xmm/m128 VPADDD ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VPADDD xmm {k}{z}, xmm, xmm/m128/m32bcst VPADDD ymm {k}{z}, ymm, ymm/m256/m32bcst VPADDD zmm {k}{z}, zmm, zmm/m512/m32bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | 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.
- VEX forms
avx-type-4- EVEX forms
AVX512-E4
Attributes
What else XED records about the forms. How to read.
- 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 VPADDD, 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_add_epi32
__m128i _mm_add_epi32(__m128i __a, __m128i __b) |
|
_mm_mask_add_epi32
__m128i _mm_mask_add_epi32(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_add_epi32
__m128i _mm_maskz_add_epi32(__mmask8 __U, __m128i __A, __m128i __B) |
|
_mm256_add_epi32
__m256i _mm256_add_epi32(__m256i __a, __m256i __b) |
|
_mm256_mask_add_epi32
__m256i _mm256_mask_add_epi32(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_add_epi32
__m256i _mm256_maskz_add_epi32(__mmask8 __U, __m256i __A, __m256i __B) |
|
_mm512_add_epi32
__m512i _mm512_add_epi32(__m512i __A, __m512i __B) |
|
_mm512_mask_add_epi32
__m512i _mm512_mask_add_epi32(__m512i __W, __mmask16 __U, __m512i __A, __m512i __B) |
|
_mm512_maskz_add_epi32
__m512i _mm512_maskz_add_epi32(__mmask16 __U, __m512i __A, __m512i __B) |
|
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.
More AVX instructions
- VMOVSHDUP
- VMOVSLDUP
- VMOVSS
- VMOVUPD
- VMOVUPS
- VMPSADBW
- VMULPD
- VMULPS
- VMULSD
- VMULSS
- VORPD
- VORPS
- VPABSB
- VPABSD
- VPABSW
- VPACKSSDW
- VPACKSSWB
- VPACKUSDW
- VPACKUSWB
- VPADDB
- VPADDQ
- VPADDSB
- VPADDSW
- VPADDUSB
- VPADDUSW
- VPADDW
- VPALIGNR
- VPAND
- VPANDN
- VPAVGB
- VPAVGW
- VPBLENDVB
- VPBLENDW
- VPCLMULQDQ
- VPCMPEQB
- VPCMPEQD
- VPCMPEQQ
- VPCMPEQW
- VPCMPESTRI
- VPCMPESTRM
More AVX2 instructions
- VBROADCASTI128
- VBROADCASTSD
- VBROADCASTSS
- VEXTRACTI128
- VGATHERDPD
- VGATHERDPS
- VGATHERQPD
- VGATHERQPS
- VINSERTI128
- VMOVNTDQA
- VMPSADBW
- VPABSB
- VPABSD
- VPABSW
- VPACKSSDW
- VPACKSSWB
- VPACKUSDW
- VPACKUSWB
- VPADDB
- VPADDQ
- VPADDSB
- VPADDSW
- VPADDUSB
- VPADDUSW
- VPADDW
- VPALIGNR
- VPAND
- VPANDN
- VPAVGB
- VPAVGW
- VPBLENDD
- VPBLENDVB
- VPBLENDW
- VPBROADCASTB
- VPBROADCASTD
- VPBROADCASTQ
- VPBROADCASTW
- VPCMPEQB
- VPCMPEQD
- VPCMPEQQ
More AVX10.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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-201 (PADDB/
PADDW/ PADDD/ PADDQ) - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- 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.