Instruction
VPMADDUBSW
Multiplies unsigned bytes of the first source by signed bytes of the second and adds adjacent products into words with signed saturation.
VPMADDUBSW multiplies bytes in pairs and adds each two neighbouring
products into a word: the bytes of the first source are read as
unsigned, those of the second as signed, and each word of the result is
a0*b0 + a1*b1, saturated to the signed 16-bit range. It is the VEX
and EVEX form of SSSE3’s PMADDUBSW: VEX for xmm
registers with AVX and ymm with AVX2, EVEX with AVX512BW for zmm
registers, write masks and 32 registers, without embedded broadcast.
Mixed signs and saturation
The operand order matters: swapping the sources reads every byte with the other signedness. One product ranges from -32,640 (255 times -128) to 32,385 (255 times 127), so the sum of two can leave the range of a word, and it is clamped to -32,768 or 32,767 without any flag. In a case recorded on Zen 5, the bytes 205 and 161 times -120 and -127 summed to -45,047 and gave -32,768. With small multipliers nothing saturates: a second source of ones adds neighbouring unsigned bytes into words, and multipliers 10 and 1 turn pairs of decimal digits into numbers from 0 to 99.
In quantized inference
Before VNNI, 8-bit inference took VPMADDUBSW with unsigned activations as the first source and signed weights as the second, then VPMADDWD with ones and VPADDD to reach 32-bit sums. VPDPBUSD fuses the three, and Intel’s optimization manual notes that it is also more accurate, since nothing saturates at 16 bits (Section 8.2.1). Because only the first operand is unsigned, the manual handles signed activations by adding 128 to them and taking 128 times the sum of the weights back out of the bias (Section 8.3.2.3).
In compiled code
For a loop that computes a[2*i]*b[2*i] + a[2*i+1]*b[2*i+1] from
uint8_t a and int8_t b and clamps it to the range of int16_t,
Clang 23 at -O2 recognizes the whole operation, saturation included,
and emits VPMADDUBSW with -march=x86-64-v3 or -march=znver5; with
-march=x86-64-v4 it widens to words instead. GCC 14 widens the bytes
and multiplies with VPMULLW.
AMD’s Zen 5 guide lists VPMADDUBSW as one macro-op with a latency of 3 cycles on every register width, as for VPMADDWD.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPMADDUBSW xmm, xmm, m128
VPMADDUBSW_XMMdq_XMMdq_MEMdq | VEX.128.66.0F38.WIG 04 /r | AVX |
VPMADDUBSW xmm, xmm, xmm
VPMADDUBSW_XMMdq_XMMdq_XMMdq | VEX.128.66.0F38.WIG 04 /r | AVX |
VPMADDUBSW ymm, ymm, m256
VPMADDUBSW_YMMqq_YMMqq_MEMqq | VEX.256.66.0F38.WIG 04 /r | AVX2 |
VPMADDUBSW ymm, ymm, ymm
VPMADDUBSW_YMMqq_YMMqq_YMMqq | VEX.256.66.0F38.WIG 04 /r | AVX2 |
VPMADDUBSW xmm {k}{z}, xmm, xmm
VPMADDUBSW_XMMi16_MASKmskw_XMMi16_XMMi16_AVX512 | EVEX.128.66.0F38.WIG 04 /r | AVX10.1 or AVX512BW + AVX512VL |
VPMADDUBSW xmm {k}{z}, xmm, m128
VPMADDUBSW_XMMi16_MASKmskw_XMMi16_MEMi16_AVX512 | EVEX.128.66.0F38.WIG 04 /r | AVX10.1 or AVX512BW + AVX512VL |
VPMADDUBSW ymm {k}{z}, ymm, ymm
VPMADDUBSW_YMMi16_MASKmskw_YMMi16_YMMi16_AVX512 | EVEX.256.66.0F38.WIG 04 /r | AVX10.1 or AVX512BW + AVX512VL |
VPMADDUBSW ymm {k}{z}, ymm, m256
VPMADDUBSW_YMMi16_MASKmskw_YMMi16_MEMi16_AVX512 | EVEX.256.66.0F38.WIG 04 /r | AVX10.1 or AVX512BW + AVX512VL |
VPMADDUBSW zmm {k}{z}, zmm, zmm
VPMADDUBSW_ZMMi16_MASKmskw_ZMMi16_ZMMi16_AVX512 | EVEX.512.66.0F38.WIG 04 /r | AVX10.1 or AVX512BW |
VPMADDUBSW zmm {k}{z}, zmm, m512
VPMADDUBSW_ZMMi16_MASKmskw_ZMMi16_MEMi16_AVX512 | EVEX.512.66.0F38.WIG 04 /r | AVX10.1 or AVX512BW |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128no mask | xmm, xmm, xmmxmm {k}{z}, xmm, xmmno maskymm {k}{z}, ymm, ymmno mask | ymm, ymm, m256ymm {k}{z}, ymm, m256no mask | ymm, ymm, ymm | xmm {k}{z}, xmm, xmmwith a mask, zeroingymm {k}{z}, ymm, ymmwith a mask, zeroing | xmm {k}{z}, xmm, m128with a mask, zeroing | ymm {k}{z}, ymm, m256with a mask, zeroing | zmm {k}{z}, zmm, zmmno mask | zmm {k}{z}, zmm, zmmwith a mask, zeroing | zmm {k}{z}, zmm, m512no mask | zmm {k}{z}, zmm, m512with a mask, zeroing |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Sandy Bridge | 11 / 1p0 | 5 / 1p0 | |||||||||
| Haswell | 11 / 1p0 | 5 / 1p0 | 12 / 1p0 | 5 / 1p0 | |||||||
| Broadwell | 10 / 1p0 | 5 / 1p0 | 11 / 1p0 | 5 / 1p0 | |||||||
| Skylake | 11 / 0.5p01 | 5 / 0.5p01 | 12 / 0.5p01 | 5 / 0.5p01 | |||||||
| Skylake-SP, Ice Lake | 11 / 0.5p01 | 5 / 0.5p01 | 12 / 0.5p01 | 5 / 0.5p01 | 5 / 0.5p01 | 11 / 0.5p01 | 12 / 0.5p01 | 5 / 0.5p05 | 5 / 0.5p05 | 12 / 0.5p05 | 12 / 0.5p05 |
| Alder Lake | 13 / 0.5p01 | 5 / 0.5p01 | 13 / 0.5p01 | 5 / 0.5p01 | |||||||
| Sapphire Rapids | 13 / 0.5p01 | 5 / 0.5p01 | 13 / 0.5p01 | 5 / 0.5p01 | 7 / 0.5p01 | 14 / 0.5p01 | 14 / 0.5p01 | 5 / 1p0 | 7 / 1p0 | 13 / 1p0 | 14 / 1p0 |
| Lunar Lake | 10 / 2V0 V1 | 4 / 2V0 V1 | 11 / 2.33V0 V1 | 4 / 2V0 V1 | |||||||
| Piledriver | 9 / 1.5FPMMA FPU0 | 4 / 1FPMMA FPU0 | |||||||||
| Zen | 11 / 1FPU0 | 4 / 1FPU0 | 11 / 2FPU0 | 4 / 2FPU0 | |||||||
| Zen 2 | 11 / 1FPU0 | 4 / 1FPU0 | 11 / 1FPU0 | 4 / 1FPU0 | |||||||
| Zen 3 | 10 / 0.5FP0 FP3 | 3 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 3 / 0.5FP0 FP3 | |||||||
| Zen 4 | 10 / 0.5FP0 FP3 | 3 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 3 / 0.5FP0 FP3 | 3 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 10 / 0.5FP0 FP3 | 3 / 1FP0 FP3 | 3 / 1FP0 FP3 | 10 / 1FP0 FP3 | 10 / 1FP0 FP3 |
| Jaguar | 7 / 1FPU0 VIMUL | 2 / 1FPU0 VIMUL | |||||||||
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.
The ymm and zmm forms repeat this in each 128-bit lane. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}.
Result word i comes from bytes 2i to 2i+1 of xmm2 and xmm3. Result words 7 to 0: sum, unchanged (bit 6 of k1 is 0), sum, sum, sum, sum, sum, sum.
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 // 16):
x = 0
for j in range(2 * i, 2 * i + 2):
x += zmm2.b[j] * src3.sb[j]
if k1[i]: # 1 without a write mask
zmm1.w[i] = ssat(x, 16)
elif zeroing:
zmm1.w[i] = 0
# else: zmm1.w[i] keeps its value
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 10 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPMADDUBSW xmm, xmm, xmm/m128 VPMADDUBSW ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VPMADDUBSW xmm {k}{z}, xmm, xmm/m128 VPMADDUBSW ymm {k}{z}, ymm, ymm/m256 VPMADDUBSW zmm {k}{z}, zmm, zmm/m512 | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128, ymm/m256, zmm/m512 | 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-E4NF
Attributes
What else XED records about the forms. How to read.
- EVEX forms
- write masking
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VPMADDUBSW, 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_maddubs_epi16
__m128i _mm_maddubs_epi16(__m128i __a, __m128i __b) |
|
_mm_mask_maddubs_epi16
__m128i _mm_mask_maddubs_epi16(__m128i __W, __mmask8 __U, __m128i __X, __m128i __Y) |
|
_mm_maskz_maddubs_epi16
__m128i _mm_maskz_maddubs_epi16(__mmask8 __U, __m128i __X, __m128i __Y) |
|
_mm256_maddubs_epi16
__m256i _mm256_maddubs_epi16(__m256i __a, __m256i __b) |
|
_mm256_mask_maddubs_epi16
__m256i _mm256_mask_maddubs_epi16(__m256i __W, __mmask16 __U, __m256i __X, __m256i __Y) |
|
_mm256_maskz_maddubs_epi16
__m256i _mm256_maskz_maddubs_epi16(__mmask16 __U, __m256i __X, __m256i __Y) |
|
_mm512_maddubs_epi16
__m512i _mm512_maddubs_epi16(__m512i __X, __m512i __Y) |
|
_mm512_mask_maddubs_epi16
__m512i _mm512_mask_maddubs_epi16(__m512i __W, __mmask32 __U, __m512i __X, __m512i __Y) |
|
_mm512_maskz_maddubs_epi16
__m512i _mm512_maskz_maddubs_epi16(__mmask32 __U, __m512i __X, __m512i __Y) |
|
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
- VPCMPISTRI
- VPCMPISTRM
- VPERM2F128
- VPERMILPD
- VPERMILPS
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPHADDD
- VPHADDSW
- VPHADDW
- VPHMINPOSUW
- VPHSUBD
- VPHSUBSW
- VPHSUBW
- VPINSRB
- VPINSRD
- VPINSRQ
- VPINSRW
- VPMADDWD
- VPMAXSB
- VPMAXSD
- VPMAXSW
- VPMAXUB
- VPMAXUD
- VPMAXUW
- VPMINSB
- VPMINSD
- VPMINSW
- VPMINUB
- VPMINUD
- VPMINUW
- VPMOVMSKB
- VPMOVSXBD
- VPMOVSXBQ
- VPMOVSXBW
- VPMOVSXDQ
- VPMOVSXWD
- VPMOVSXWQ
More AVX2 instructions
- VPCMPEQW
- VPCMPGTB
- VPCMPGTD
- VPCMPGTQ
- VPCMPGTW
- VPERM2I128
- VPERMD
- VPERMPD
- VPERMPS
- VPERMQ
- VPGATHERDD
- VPGATHERDQ
- VPGATHERQD
- VPGATHERQQ
- VPHADDD
- VPHADDSW
- VPHADDW
- VPHSUBD
- VPHSUBSW
- VPHSUBW
- VPMADDWD
- VPMASKMOVD
- VPMASKMOVQ
- VPMAXSB
- VPMAXSD
- VPMAXSW
- VPMAXUB
- VPMAXUD
- VPMAXUW
- VPMINSB
- VPMINSD
- VPMINSW
- VPMINUB
- VPMINUD
- VPMINUW
- VPMOVMSKB
- VPMOVSXBD
- VPMOVSXBQ
- VPMOVSXBW
- VPMOVSXDQ
More AVX10.1 instructions
- VPEXPANDB
- VPEXPANDD
- VPEXPANDQ
- VPEXPANDW
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPGATHERDD
- VPGATHERDQ
- VPGATHERQD
- VPGATHERQQ
- VPINSRB
- VPINSRD
- VPINSRQ
- VPINSRW
- VPLZCNTD
- VPLZCNTQ
- VPMADD52HUQ
- VPMADD52LUQ
- VPMADDWD
- VPMAXSB
- VPMAXSD
- VPMAXSQ
- VPMAXSW
- VPMAXUB
- VPMAXUD
- VPMAXUQ
- VPMAXUW
- VPMINSB
- VPMINSD
- VPMINSQ
- VPMINSW
- VPMINUB
- VPMINUD
- VPMINUQ
- VPMINUW
- VPMOVB2M
- VPMOVD2M
- VPMOVDB
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-310 (PMADDUBSW)
- 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)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 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.