Extensions
Forms
6 (6 EVEX)
Data
Intel XED v2026.08.23

VPOPCNTD counts the set bits of each doubleword, as POPCNT does for one register. It belongs to AVX512_VPOPCNTDQ with VPOPCNTQ, which counts quadwords; the byte and word counts, VPOPCNTB and VPOPCNTW, came separately in AVX512_BITALG. Neither extension is part of x86-64-v4, so a compiler needs -mavx512vpopcntdq or a -march naming a processor that has it. AMD’s Zen 5 guide lists AVX512_VPOPCNTDQ among Zen 5’s extensions.

What it replaces

Without it, vector code counts bits with a table of the 16 nibble counts in a register: VPSHUFB looks up the low and the high nibble of every byte, an addition gives per-byte counts, and VPSADBW against zero sums bytes into larger elements. For a vector of eight __builtin_popcount results, Clang 23 at -O2 with -march=x86-64-v4 emits that sequence, 14 instructions in all, and with -mavx512vpopcntdq a single VPOPCNTD; GCC 14 emits VPOPCNTD too once allowed. Clang also vectorizes a loop of __builtin_popcount into VPOPCNTD, where GCC keeps the scalar POPCNT.

Uses

  • Per-element counts: the number of set flags in each of many bitmaps, or the Hamming distance of pairs of 32-bit codes after a VPXORD.
  • The weight of a whole buffer, summed into a vector of counts that is reduced once at the end. For that, VPOPCNTQ halves the number of elements to add up.
  • Masks are not its job: the bits of a mask register are counted with KMOVW and the scalar POPCNT.

AMD’s Zen 5 guide lists VPOPCNTD as one macro-op with a latency of 2 cycles on XMM, YMM and ZMM registers alike.

Forms

Every encoding of VPOPCNTD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPOPCNTD zmm {k}{z}, zmm VPOPCNTD_ZMMu32_MASKmskw_ZMMu32_AVX512EVEX.512.66.0F38.W0 55 /rAVX10.1 or AVX512_VPOPCNTDQ
VPOPCNTD zmm {k}{z}, m512/m32bcst VPOPCNTD_ZMMu32_MASKmskw_MEMu32_AVX512EVEX.512.66.0F38.W0 55 /rAVX10.1 or AVX512_VPOPCNTDQ
VPOPCNTD xmm {k}{z}, xmm VPOPCNTD_XMMu32_MASKmskw_XMMu32_AVX512EVEX.128.66.0F38.W0 55 /rAVX10.1 or AVX512_VPOPCNTDQ + AVX512VL
VPOPCNTD xmm {k}{z}, m128/m32bcst VPOPCNTD_XMMu32_MASKmskw_MEMu32_AVX512EVEX.128.66.0F38.W0 55 /rAVX10.1 or AVX512_VPOPCNTDQ + AVX512VL
VPOPCNTD ymm {k}{z}, ymm VPOPCNTD_YMMu32_MASKmskw_YMMu32_AVX512EVEX.256.66.0F38.W0 55 /rAVX10.1 or AVX512_VPOPCNTDQ + AVX512VL
VPOPCNTD ymm {k}{z}, m256/m32bcst VPOPCNTD_YMMu32_MASKmskw_MEMu32_AVX512EVEX.256.66.0F38.W0 55 /rAVX10.1 or AVX512_VPOPCNTDQ + 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.
Modelzmm {k}{z}, zmmzmm {k}{z}, m512/m32bcstxmm {k}{z}, xmmxmm {k}{z}, m128/m32bcstymm {k}{z}, ymmymm {k}{z}, m256/m32bcst
Ice Lake1 / 1p08 / 1p01 / 0.5p017 / 0.5p011 / 0.5p018 / 0.5p01
Sapphire Rapids3 / 1p511 / 1p53 / 1p510 / 1p53 / 1p511 / 1p5
Zen 41 / 0.51FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP32 / 12FP0 FP18 / 0.5FP0 FP1 FP2 FP31 / 0.253FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP3
  1. Zen 4 model: AMD's spreadsheets give latency 2 for Zen 4 and Zen 5 (AMD 57647, row 2763; AMD 58455, row 923).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 2761; AMD 58455, row 923).
  3. Zen 4 model: AMD's spreadsheets give latency 2 for Zen 4 and Zen 5 (AMD 57647, row 2762; AMD 58455, row 923).

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 doubleword of the result comes from the doubleword in the same place in each source.
VPOPCNTD: element by elementResult doubleword i comes from doubleword i of xmm2. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.0123xmm2or m128a1110k1r0r1r3xmm1

Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms. The 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. Result doublewords 3 to 0: r3, unchanged (bit 2 of k1 is 0), r1, r0.

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]:
        zmm1.d[i] = popcount(src2.d[i])
    elif zeroing:
        zmm1.d[i] = 0
    # else: zmm1.d[i] keeps its value
# m32bcst: src2.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 6 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
VPOPCNTD xmm {k}{z}, xmm/m128/m32bcst VPOPCNTD ymm {k}{z}, ymm/m256/m32bcst VPOPCNTD zmm {k}{z}, zmm/m512/m32bcst
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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.

All forms
AVX512-E4

Attributes

What else XED records about the forms. How to read.

All forms
write masking
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VPOPCNTD, 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_popcnt_epi32 __m128i _mm_popcnt_epi32(__m128i __A)

VPOPCNTD xmm, xmm EVEX.128 -mavx512vpopcntdq -mavx512vl

_mm_mask_popcnt_epi32 __m128i _mm_mask_popcnt_epi32(__m128i __W, __mmask8 __U, __m128i __A)

VPOPCNTD xmm {k}, xmm EVEX.128 -mavx512vpopcntdq -mavx512vl

_mm_maskz_popcnt_epi32 __m128i _mm_maskz_popcnt_epi32(__mmask8 __U, __m128i __A)

VPOPCNTD xmm {k}{z}, xmm EVEX.128 -mavx512vpopcntdq -mavx512vl

_mm256_popcnt_epi32 __m256i _mm256_popcnt_epi32(__m256i __A)

VPOPCNTD ymm, ymm EVEX.256 -mavx512vpopcntdq -mavx512vl

_mm256_mask_popcnt_epi32 __m256i _mm256_mask_popcnt_epi32(__m256i __W, __mmask8 __U, __m256i __A)

VPOPCNTD ymm {k}, ymm EVEX.256 -mavx512vpopcntdq -mavx512vl

_mm256_maskz_popcnt_epi32 __m256i _mm256_maskz_popcnt_epi32(__mmask8 __U, __m256i __A)

VPOPCNTD ymm {k}{z}, ymm EVEX.256 -mavx512vpopcntdq -mavx512vl

_mm512_popcnt_epi32 __m512i _mm512_popcnt_epi32(__m512i __A)

VPOPCNTD zmm, zmm EVEX.512 -mavx512vpopcntdq

_mm512_mask_popcnt_epi32 __m512i _mm512_mask_popcnt_epi32(__m512i __W, __mmask16 __U, __m512i __A)

VPOPCNTD zmm {k}, zmm EVEX.512 -mavx512vpopcntdq

_mm512_maskz_popcnt_epi32 __m512i _mm512_maskz_popcnt_epi32(__mmask16 __U, __m512i __A)

VPOPCNTD zmm {k}{z}, zmm EVEX.512 -mavx512vpopcntdq

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
AVX512_VPOPCNTDQ_512

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

or

AVX512_VPOPCNTDQ
CPUID.(EAX=07H,ECX=0):ECX[14] AVX512_VPOPCNTDQ

Ice Lake (client), Tiger Lake, Nova Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512_VPOPCNTDQ_128

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

or

AVX512_VPOPCNTDQ + AVX512VL
CPUID.(EAX=07H,ECX=0):ECX[14] AVX512_VPOPCNTDQ
CPUID.(EAX=07H,ECX=0):EBX[31] AVX512VL

Ice Lake (client), Tiger Lake, Nova Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 4, Zen 5, Zen 6
AVX512_VPOPCNTDQ_256
Same as AVX512_VPOPCNTDQ_128Same as AVX512_VPOPCNTDQ_128

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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-606 (VPOPCNT)
  7. 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.