Instruction
PADDW
Adds packed words of MMX or XMM registers, wrapping around on overflow.
PADDW adds words element by element and keeps the low 16 bits of each
sum, wrapping around the same way for signed and unsigned words: 8 in
an XMM register, 4 in an MMX register. PADDB covers
what the family’s legacy forms share. On Zen 5, the recorded paddw xmm4, [mem] turned 7FFFh plus 0001h into 8000h (32767 plus 1 wrapping
to -32768) and FFFFh plus FFFFh into FFFEh, leaving bits 255:128 of the
register as they were (see mixing SSE and
AVX). The additions that clamp instead of
wrapping are PADDSW for signed words and
PADDUSW for unsigned ones.
Words in compiled code
In our builds at -O2 for the x86-64 baseline:
int16_tanduint16_tarrays.a[i] = b[i] + c[i]is one PADDW per 8 words in GCC 14 and Clang 23, both operands loaded by MOVDQU.- Widening sums of bytes.
(int16_t)b[i] + (int16_t)c[i]overint8_tarrays, which keeps the full range of the sum in a word, has both compilers sign-extend each byte to a word before PADDW, but differently: GCC compares each input with a zeroed register by PCMPGTB to get a sign mask and interleaves it with PUNPCKLBW and PUNPCKHBW, where Clang duplicates each byte onto itself with PUNPCKLBW and shifts right by 8 with PSRAW instead.
AMD’s latency spreadsheet for Zen 5 gives PADDW one cycle, four per cycle, on all four vector pipes. The MMX form came with MMX and the XMM form with SSE2, whose memory operand must be aligned to 16 bytes. VPADDW is the VEX and EVEX form; PADDQ takes quadword elements.
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.
Every word works alike: 4 and 8 words in the mm and xmm forms.
Result word i comes from word i of xmm1 and xmm2. Result words 7 to 0: a7+b7, a6+b6, a5+b5, a4+b4, a3+b3, a2+b2, a1+b1, a0+b0.
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
PADDW mm, mm/m64for i in range(4):
mm1.w[i] = mm1.w[i] + src2.w[i]
# x87: TOP = 0, all tags valid, bits 79:64 of mm1's register all onesRun on AMD Zen 5 (EPYC 9645): 2 cases.
PADDW xmm, xmm/m128for i in range(8):
xmm1.w[i] = xmm1.w[i] + src2.w[i]
# bits 128 and up of the register are unchangedRun on AMD Zen 5 (EPYC 9645): 2 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
PADDW mm, mm/m64 | ||
mm | explicit | read, write |
mm/m64 | explicit | read |
PADDW xmm, xmm/m128 | ||
xmm | explicit | read, write |
xmm/m128 | 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.
Attributes
What else XED records about the forms. How to read.
PADDW mm, mm/m64- may abort a TSX transaction
PADDW xmm, m128- aligned memory operand
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to PADDW, 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_epi16
__m128i _mm_add_epi16(__m128i __a, __m128i __b) |
|
_mm_add_pi16
__m64 _mm_add_pi16(__m64 __m1, __m64 __m2) |
|
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 MMX instructions
- EMMS
- MOVD
- MOVQ
- PACKSSDW
- PACKSSWB
- PACKUSWB
- PADDB
- PADDD
- PADDSB
- PADDSW
- PADDUSB
- PADDUSW
- PAND
- PANDN
- PCMPEQB
- PCMPEQD
- PCMPEQW
- PCMPGTB
- PCMPGTD
- PCMPGTW
- PMADDWD
- PMULHW
- PMULLW
- POR
- PSLLD
- PSLLQ
- PSLLW
- PSRAD
- PSRAW
- PSRLD
- PSRLQ
- PSRLW
- PSUBB
- PSUBD
- PSUBSB
- PSUBSW
- PSUBUSB
- PSUBUSW
- PSUBW
- PUNPCKHBW
More SSE2 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-201 (PADDB/
PADDW/ PADDD/ PADDQ) - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 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, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.