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

VPSADBW is PSADBW in VEX and EVEX encodings: per quadword, the absolute differences of eight pairs of unsigned bytes are added, and the total, at most 2040, goes to bits 15:0 of the quadword with the rest cleared. The PSADBW page explains the instruction and its two classic uses, block matching and summing bytes against a zero register. What changes here is the width and the encoding:

  • Three operands. The destination is separate from both sources, so neither input is lost, and a memory operand needs no alignment.
  • Wider vectors. AVX2 gives four sums in a YMM register and AVX512BW eight in a ZMM register. The VEX.128 form clears the register from bit 128 up, as every VEX and EVEX form clears it above its width.
  • No write mask. The EVEX forms take neither a mask nor a broadcast: unlike most AVX-512 integer instructions, VPSADBW has no {k} operand at any width, and its intrinsics have no _mask variants. What EVEX adds is the registers from XMM16 to XMM31, such as XMM29 and YMM24 in the cases recorded on Zen 5.

In compiled code

For s += abs(p[i] - q[i]) over uint8_t arrays of a constant length of 1024, GCC 14 at -O2 emits one VPSADBW per 32 bytes with -march=x86-64-v3 and per 64 bytes with -march=x86-64-v4, and adds the quadword sums with VPADDD. Clang 23 loads eight bytes at a time with VMOVQ and uses the 128-bit form on them, under either target. When the length is a variable, GCC keeps the loop scalar.

The zero-register trick is how Clang 23 finishes a population count without hardware support for vectors: for __builtin_popcountll over a uint64_t array with -march=x86-64-v3 or -march=x86-64-v4 (neither includes AVX512_VPOPCNTDQ), it counts the bits of each byte with two VPSHUFB lookups, one per nibble, and then VPSADBW against zero adds the eight byte counts of each quadword, which VPADDQ accumulates. GCC 14 uses the scalar POPCNT instead.

VDBPSADBW of AVX512BW is the instruction that does take a mask: it computes sums of four bytes, after shuffling the second source.

Forms

Every encoding of VPSADBW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPSADBW xmm, xmm, m128 VPSADBW_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG F6 /rAVX
VPSADBW xmm, xmm, xmm VPSADBW_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG F6 /rAVX
VPSADBW ymm, ymm, m256 VPSADBW_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG F6 /rAVX2
VPSADBW ymm, ymm, ymm VPSADBW_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG F6 /rAVX2
VPSADBW xmm, xmm, xmm VPSADBW_XMMu16_XMMu8_XMMu8_AVX512EVEX.128.66.0F.WIG F6 /rAVX10.1 or AVX512BW + AVX512VL
VPSADBW xmm, xmm, m128 VPSADBW_XMMu16_XMMu8_MEMu8_AVX512EVEX.128.66.0F.WIG F6 /rAVX10.1 or AVX512BW + AVX512VL
VPSADBW ymm, ymm, ymm VPSADBW_YMMu16_YMMu8_YMMu8_AVX512EVEX.256.66.0F.WIG F6 /rAVX10.1 or AVX512BW + AVX512VL
VPSADBW ymm, ymm, m256 VPSADBW_YMMu16_YMMu8_MEMu8_AVX512EVEX.256.66.0F.WIG F6 /rAVX10.1 or AVX512BW + AVX512VL
VPSADBW zmm, zmm, zmm VPSADBW_ZMMu16_ZMMu8_ZMMu8_AVX512EVEX.512.66.0F.WIG F6 /rAVX10.1 or AVX512BW
VPSADBW zmm, zmm, m512 VPSADBW_ZMMu16_ZMMu8_MEMu8_AVX512EVEX.512.66.0F.WIG F6 /rAVX10.1 or AVX512BW

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, m128xmm, xmm, xmm
ymm, ymm, ymm
ymm, ymm, m256ymm, ymm, ymmzmm, zmm, zmmzmm, zmm, m512
Sandy Bridge11 / 1p05 / 1p0
Haswell11 / 1p05 / 1p012 / 1p05 / 1p0
Broadwell10 / 1p05 / 1p011 / 1p05 / 1p0
Skylake9 / 1p53 / 1p510 / 1p53 / 1p5
Skylake-SP, Ice Lake9 / 1p53 / 1p510 / 1p53 / 1p53 / 1p510 / 1p5
Alder Lake10 / 1p53 / 1p511 / 1p53 / 1p5
Sapphire Rapids10 / 1p53 / 1p511 / 1p53 / 1p53 / 1p511 / 1p5
Lunar Lake10 / 0.5V2 V33 / 0.5V2 V311 / 0.5V2 V33 / 0.5V2 V3
Piledriver9 / 1.5FPMAL FPU0 FPU14 / 1FPMAL FPU0 FPU1
Zen10 / 1FPU03 / 1FPU010 / 2FPU03 / 2FPU0
Zen 210 / 1FPU03 / 1FPU010 / 1FPU03 / 1FPU0
Zen 310 / 0.5FP0 FP1 FP2 FP33 / 0.5FP0 FP1 FP2 FP310 / 0.5FP0 FP1 FP2 FP33 / 0.5FP0 FP1 FP2 FP3
Zen 410 / 0.5FP0 FP1 FP2 FP33 / 0.5FP0 FP1 FP2 FP310 / 0.5FP0 FP1 FP2 FP33 / 0.5FP0 FP1 FP2 FP34 / 11FP0 FP1 FP2 FP311 / 1FP0 FP1 FP2 FP3
Jaguar7 / 1FPU0 FPU1 VALU0 VALU12 / 0.5FPU0 FPU1 VALU0 VALU1
  1. Zen 4 model: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 2827; AMD 58455, row 292).

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.

Groups of 8 adjacent bytes are combined into one quadword.
VPSADBW: groups of 8 elementsResult quadword i comes from bytes 8i to 8i+7 of xmm2 and xmm3. Result quadwords 1 to 0: sum, sum.0123456789101112131415xmm2asumsumxmm10123456789101112131415xmm3or m128b

The ymm and zmm forms repeat this in each 128-bit lane.

Result quadword i comes from bytes 8i to 8i+7 of xmm2 and xmm3. Result quadwords 1 to 0: 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 // 64):
    x = 0
    for j in range(8 * i, 8 * i + 8):
        x += abs(zmm2.b[j] - src3.b[j])
    zmm1.q[i] = x
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 10 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
VPSADBW xmm, xmm, xmm/m128 VPSADBW ymm, ymm, ymm/m256 VPSADBW zmm, zmm, zmm/m512
xmm, ymm, zmmexplicitwrite
xmm, ymm, zmmexplicitread
xmm/m128, ymm/m256, zmm/m512explicitread

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

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPSADBW, 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_sad_epu8 __m128i _mm_sad_epu8(__m128i __a, __m128i __b)

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

_mm256_sad_epu8 __m256i _mm256_sad_epu8(__m256i __a, __m256i __b)

VPSADBW ymm, ymm, ymm VEX.256 -mavx2

_mm512_sad_epu8 __m512i _mm512_sad_epu8(__m512i __A, __m512i __B)

VPSADBW zmm, zmm, zmm EVEX.512 -mavx512bw

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
AVX2

AVX2
CPUID.(EAX=07H,ECX=0):EBX[5] AVX2

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, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX512BW_128

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

or

AVX512BW + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW
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
AVX512BW_256
Same as AVX512BW_128Same as AVX512BW_128
AVX512BW_512

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

or

AVX512BW
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW

Same as AVX512BW_128

More AVX instructions

All 253 AVX instructions

More AVX2 instructions

All 138 AVX2 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-418 (PSADBW)
  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)

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.