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

VPOPCNTQ counts the set bits of each quadword and writes the count, 0 to 64, to the same element, as POPCNT does for one register. It is the quadword form of VPOPCNTD, whose page describes AVX512_VPOPCNTDQ, the nibble-table code it replaces and the flags a compiler needs, since x86-64-v4 does not include it. It takes masking and a broadcast quadword.

Recorded on Zen 5

  • The extremes. All ones counted 40h, 7FFFFFFFFFFFFFFFh 3Fh and 8000000000000000h 1, also as a broadcast: vpopcntq zmm24{k6}, qword bcst [mem] wrote 1 to the three elements K6’s low byte, A4h, selected and kept the other five.
  • Zeroing. vpopcntq ymm0{k7}{z}, ymm31, with E3h in K7’s low byte, wrote the counts of elements 0 and 1, 0 and 1, and zeroed elements 2 and 3.

Counting quadwords without it

For o[i] = __builtin_popcountll(a[i]) over uint64_t arrays, GCC 14 and Clang 23 at -O2 with -march=znver5 load and count 8 quadwords with one vpopcntq zmm0, zmmword ptr [...]; summing all the counts, GCC adds the vectors with VPADDQ and reduces at the end. With -march=x86-64-v4, GCC keeps a scalar POPCNT per element, and Clang counts the nibbles of each byte with VPSHUFB and adds the eight bytes of each quadword with VPSADBW against zero, which leaves one count per quadword: seven instructions per vector where VPOPCNTQ needs one.

AMD’s Zen 5 latency spreadsheet gives VPOPCNTQ 2 cycles and two per cycle on pipes FP0 and FP3, as VPOPCNTD.

Forms

Every encoding of VPOPCNTQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPOPCNTQ zmm {k}{z}, zmm VPOPCNTQ_ZMMu64_MASKmskw_ZMMu64_AVX512EVEX.512.66.0F38.W1 55 /rAVX10.1 or AVX512_VPOPCNTDQ
VPOPCNTQ zmm {k}{z}, m512/m64bcst VPOPCNTQ_ZMMu64_MASKmskw_MEMu64_AVX512EVEX.512.66.0F38.W1 55 /rAVX10.1 or AVX512_VPOPCNTDQ
VPOPCNTQ xmm {k}{z}, xmm VPOPCNTQ_XMMu64_MASKmskw_XMMu64_AVX512EVEX.128.66.0F38.W1 55 /rAVX10.1 or AVX512_VPOPCNTDQ + AVX512VL
VPOPCNTQ xmm {k}{z}, m128/m64bcst VPOPCNTQ_XMMu64_MASKmskw_MEMu64_AVX512EVEX.128.66.0F38.W1 55 /rAVX10.1 or AVX512_VPOPCNTDQ + AVX512VL
VPOPCNTQ ymm {k}{z}, ymm VPOPCNTQ_YMMu64_MASKmskw_YMMu64_AVX512EVEX.256.66.0F38.W1 55 /rAVX10.1 or AVX512_VPOPCNTDQ + AVX512VL
VPOPCNTQ ymm {k}{z}, m256/m64bcst VPOPCNTQ_YMMu64_MASKmskw_MEMu64_AVX512EVEX.256.66.0F38.W1 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/m64bcstxmm {k}{z}, xmmxmm {k}{z}, m128/m64bcstymm {k}{z}, ymmymm {k}{z}, m256/m64bcst
Ice Lake1 / 1p08 / 1p01 / 0.5p017 / 0.5p011 / 0.5p018 / 0.5p01
Sapphire Rapids3 / 1p511 / 1p53 / 1p510 / 1p53 / 1p511 / 1p5
Zen 41 / 0.5FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP32 / 1FP0 FP18 / 0.5FP0 FP1 FP2 FP31 / 0.25FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP3

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 quadword of the result comes from the quadword in the same place in each source.
VPOPCNTQ: element by elementResult quadword i comes from quadword i of xmm2. Result quadwords 1 to 0: r1, r0.01xmm2or m128a11k1r0r1xmm1

Every quadword works alike: 2, 4 and 8 quadwords 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 m64bcst, one quadword from memory stands for every element of the last source.

Result quadword i comes from quadword i of xmm2. Result quadwords 1 to 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 // 64):
    if k1[i]:
        zmm1.q[i] = popcount(src2.q[i])
    elif zeroing:
        zmm1.q[i] = 0
    # else: zmm1.q[i] keeps its value
# m64bcst: src2.q[i] is the m64 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
VPOPCNTQ xmm {k}{z}, xmm/m128/m64bcst VPOPCNTQ ymm {k}{z}, ymm/m256/m64bcst VPOPCNTQ zmm {k}{z}, zmm/m512/m64bcst
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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 VPOPCNTQ, 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_epi64 __m128i _mm_popcnt_epi64(__m128i __A)

VPOPCNTQ xmm, xmm EVEX.128 -mavx512vpopcntdq -mavx512vl

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

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

_mm_maskz_popcnt_epi64 __m128i _mm_maskz_popcnt_epi64(__mmask8 __U, __m128i __A)

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

_mm256_popcnt_epi64 __m256i _mm256_popcnt_epi64(__m256i __A)

VPOPCNTQ ymm, ymm EVEX.256 -mavx512vpopcntdq -mavx512vl

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

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

_mm256_maskz_popcnt_epi64 __m256i _mm256_maskz_popcnt_epi64(__mmask8 __U, __m256i __A)

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

_mm512_popcnt_epi64 __m512i _mm512_popcnt_epi64(__m512i __A)

VPOPCNTQ zmm, zmm EVEX.512 -mavx512vpopcntdq

_mm512_mask_popcnt_epi64 __m512i _mm512_mask_popcnt_epi64(__m512i __W, __mmask8 __U, __m512i __A)

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

_mm512_maskz_popcnt_epi64 __m512i _mm512_maskz_popcnt_epi64(__mmask8 __U, __m512i __A)

VPOPCNTQ 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.