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

VPLZCNTQ counts the zero bits above the highest set bit of each quadword, as LZCNT does for one 64-bit register: 0 for an element with its top bit set, 64 for a zero element. It is the quadword form of VPLZCNTD, whose page shows how the count gives trailing zeros and how it turns a VPCONFLICTQ result into the position of the nearest equal element. It belongs to AVX512CD, takes a write mask and a broadcast quadword, and needs AVX512VL below 512 bits.

Recorded on Zen 5

  • The ends. vplzcntq zmm1{k3}, zmm2 gave 0 for 8000000000000000h, 1 for 7FFFFFFFFFFFFFFFh, 40h for 0 and 3Ch for 0Fh, in the elements K3 selects.
  • Broadcast. A broadcast 1 gave 3Fh, 63, in every selected element.
  • Zeroing. vplzcntq ymm0{k5}{z}, ymm31 with only bit 0 of the four set wrote 3Fh for 1 and zeroed the other three elements and the register from bit 256 up.

In compiled code

At -O2 with -march=x86-64-v4, both compilers vectorize a loop of __builtin_clzg(a[i], 64) over uint64_t arrays with VPLZCNTQ, GCC 14 on ZMM registers with the operand in memory and Clang 23 on YMM registers. For __builtin_ctzg(a[i], 64) both use the sequence of VPLZCNTD’s page in 64 bits: VPADDQ of -1, VPANDNQ, VPLZCNTQ and a VPSUBQ from 64. _mm512_lzcnt_epi64 is one VPLZCNTQ.

AMD’s Zen 5 latency spreadsheet gives one macro-op with 2 cycles at every width, two per cycle on pipes FP0 and FP3, as for VPLZCNTD.

Forms

Every encoding of VPLZCNTQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPLZCNTQ zmm {k}{z}, zmm VPLZCNTQ_ZMMu64_MASKmskw_ZMMu64_AVX512CDEVEX.512.66.0F38.W1 44 /rAVX10.1 or AVX512CD
VPLZCNTQ zmm {k}{z}, m512/m64bcst VPLZCNTQ_ZMMu64_MASKmskw_MEMu64_AVX512CDEVEX.512.66.0F38.W1 44 /rAVX10.1 or AVX512CD
VPLZCNTQ xmm {k}{z}, xmm VPLZCNTQ_XMMu64_MASKmskw_XMMu64_AVX512EVEX.128.66.0F38.W1 44 /rAVX10.1 or AVX512CD + AVX512VL
VPLZCNTQ xmm {k}{z}, m128/m64bcst VPLZCNTQ_XMMu64_MASKmskw_MEMu64_AVX512EVEX.128.66.0F38.W1 44 /rAVX10.1 or AVX512CD + AVX512VL
VPLZCNTQ ymm {k}{z}, ymm VPLZCNTQ_YMMu64_MASKmskw_YMMu64_AVX512EVEX.256.66.0F38.W1 44 /rAVX10.1 or AVX512CD + AVX512VL
VPLZCNTQ ymm {k}{z}, m256/m64bcst VPLZCNTQ_YMMu64_MASKmskw_MEMu64_AVX512EVEX.256.66.0F38.W1 44 /rAVX10.1 or AVX512CD + 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}, xmm
ymm {k}{z}, ymm
xmm {k}{z}, m128/m64bcstymm {k}{z}, m256/m64bcst
Skylake-SP, Ice Lake5 / 0.5p0512 / 0.5p055 / 0.5p0111 / 0.5p0112 / 0.5p01
Sapphire Rapids4 / 1p012 / 1p04 / 0.5p0111 / 0.5p0112 / 0.5p01
Zen 42 / 1FP0 FP110 / 1FP0 FP32 / 1FP0 FP110 / 0.5FP0 FP310 / 0.5FP0 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.
VPLZCNTQ: 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] = lzcnt(src2.q[i], 64)
    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
VPLZCNTQ xmm {k}{z}, xmm/m128/m64bcst VPLZCNTQ ymm {k}{z}, ymm/m256/m64bcst VPLZCNTQ 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 VPLZCNTQ, 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_lzcnt_epi64 __m128i _mm_lzcnt_epi64(__m128i __A)

VPLZCNTQ xmm, xmm EVEX.128 -mavx512vl -mavx512cd

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

VPLZCNTQ xmm {k}, xmm EVEX.128 -mavx512vl -mavx512cd

_mm_maskz_lzcnt_epi64 __m128i _mm_maskz_lzcnt_epi64(__mmask8 __U, __m128i __A)

VPLZCNTQ xmm {k}{z}, xmm EVEX.128 -mavx512vl -mavx512cd

_mm256_lzcnt_epi64 __m256i _mm256_lzcnt_epi64(__m256i __A)

VPLZCNTQ ymm, ymm EVEX.256 -mavx512vl -mavx512cd

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

VPLZCNTQ ymm {k}, ymm EVEX.256 -mavx512vl -mavx512cd

_mm256_maskz_lzcnt_epi64 __m256i _mm256_maskz_lzcnt_epi64(__mmask8 __U, __m256i __A)

VPLZCNTQ ymm {k}{z}, ymm EVEX.256 -mavx512vl -mavx512cd

_mm512_lzcnt_epi64 __m512i _mm512_lzcnt_epi64(__m512i __A)

VPLZCNTQ zmm, zmm EVEX.512 -mavx512cd

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

VPLZCNTQ zmm {k}, zmm EVEX.512 -mavx512cd

_mm512_maskz_lzcnt_epi64 __m512i _mm512_maskz_lzcnt_epi64(__mmask8 __U, __m512i __A)

VPLZCNTQ zmm {k}{z}, zmm EVEX.512 -mavx512cd

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
AVX512CD_512

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

or

AVX512CD
CPUID.(EAX=07H,ECX=0):EBX[28] AVX512CD

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, Knights Landing, Knights Mill, Zen 4, Zen 5, Zen 6
AVX512CD_128

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

or

AVX512CD + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[28] AVX512CD
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
AVX512CD_256
Same as AVX512CD_128Same as AVX512CD_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-562 (VPLZCNTD/Q)
  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.