Instruction
VPLZCNTD
Counts the leading zero bits of each doubleword.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPLZCNTD counts the zero bits above the highest set bit of each doubleword, as LZCNT does for one register: 0 for an element with its top bit set, 32 for a zero element. Every input has a defined result. It belongs to AVX512CD, part of x86-64-v4, and VPLZCNTQ counts in quadwords; there is no byte or word form.
In compiled code
With -march=x86-64-v4, Clang 23 at -O2 vectorizes a loop of
__builtin_clz into VPLZCNTD, and since the zero case is defined, also
a ? __builtin_clz(a) : 32 and 32 - __builtin_clzg(a, 32), the bit
width of each element; GCC 14 keeps such loops scalar with LZCNT, but
emits VPLZCNTD for the same operations applied to the elements of a
vector type. With only AVX2 there is no per-element count, and the
same eight __builtin_clzg cost Clang 19 instructions.
Counting trailing zeros needs no instruction of its own: (x - 1) & ~x sets exactly the bits below the lowest set bit, and 32 minus their
leading-zero count is the trailing-zero count. Both compilers compile
a vector of __builtin_ctzg(x, 32) to that sequence, a VPADDD of -1,
VPANDN, VPLZCNTD and a subtraction from 32.
With VPCONFLICTD
Intel’s optimization manual pairs it with VPCONFLICTD (Section 17.16.1): the conflict result of an element has bit j set for each equal element j below it, so 31 minus its leading-zero count is the position of the nearest equal element, and -1 where there is none. That vector serves as the index of VPERMD to bring each element the value it must be combined with (Figure 17-15, Example 17-24).
AMD’s Zen 5 guide lists VPLZCNTD as one macro-op with a latency of 2 cycles on XMM, YMM and ZMM registers alike.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPLZCNTD zmm {k}{z}, zmm
VPLZCNTD_ZMMu32_MASKmskw_ZMMu32_AVX512CD | EVEX.512.66.0F38.W0 44 /r | AVX10.1 or AVX512CD |
VPLZCNTD zmm {k}{z}, m512/m32bcst
VPLZCNTD_ZMMu32_MASKmskw_MEMu32_AVX512CD | EVEX.512.66.0F38.W0 44 /r | AVX10.1 or AVX512CD |
VPLZCNTD xmm {k}{z}, xmm
VPLZCNTD_XMMu32_MASKmskw_XMMu32_AVX512 | EVEX.128.66.0F38.W0 44 /r | AVX10.1 or AVX512CD + AVX512VL |
VPLZCNTD xmm {k}{z}, m128/m32bcst
VPLZCNTD_XMMu32_MASKmskw_MEMu32_AVX512 | EVEX.128.66.0F38.W0 44 /r | AVX10.1 or AVX512CD + AVX512VL |
VPLZCNTD ymm {k}{z}, ymm
VPLZCNTD_YMMu32_MASKmskw_YMMu32_AVX512 | EVEX.256.66.0F38.W0 44 /r | AVX10.1 or AVX512CD + AVX512VL |
VPLZCNTD ymm {k}{z}, m256/m32bcst
VPLZCNTD_YMMu32_MASKmskw_MEMu32_AVX512 | EVEX.256.66.0F38.W0 44 /r | AVX10.1 or AVX512CD + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, zmm | zmm {k}{z}, m512/m32bcst | xmm {k}{z}, xmmymm {k}{z}, ymm | xmm {k}{z}, m128/m32bcst | ymm {k}{z}, m256/m32bcst |
|---|---|---|---|---|---|
| Skylake-SP, Ice Lake | 5 / 0.5p05 | 12 / 0.5p05 | 5 / 0.5p01 | 11 / 0.5p01 | 12 / 0.5p01 |
| Sapphire Rapids | 4 / 1p0 | 12 / 1p0 | 4 / 0.5p01 | 11 / 0.5p01 | 12 / 0.5p01 |
| Zen 4 | 2 / 1FP0 FP1 | 10 / 1FP0 FP3 | 2 / 11FP0 FP1 | 10 / 0.5FP0 FP3 | 10 / 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.
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] = lzcnt(src2.d[i], 32)
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 upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPLZCNTD xmm {k}{z}, xmm/m128/m32bcst VPLZCNTD ymm {k}{z}, ymm/m256/m32bcst VPLZCNTD zmm {k}{z}, zmm/m512/m32bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | 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.
- 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 VPLZCNTD, 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_lzcnt_epi32
__m128i _mm_lzcnt_epi32(__m128i __A) |
|
_mm_mask_lzcnt_epi32
__m128i _mm_mask_lzcnt_epi32(__m128i __W, __mmask8 __U, __m128i __A) |
|
_mm_maskz_lzcnt_epi32
__m128i _mm_maskz_lzcnt_epi32(__mmask8 __U, __m128i __A) |
|
_mm256_lzcnt_epi32
__m256i _mm256_lzcnt_epi32(__m256i __A) |
|
_mm256_mask_lzcnt_epi32
__m256i _mm256_mask_lzcnt_epi32(__m256i __W, __mmask8 __U, __m256i __A) |
|
_mm256_maskz_lzcnt_epi32
__m256i _mm256_maskz_lzcnt_epi32(__mmask8 __U, __m256i __A) |
|
_mm512_lzcnt_epi32
__m512i _mm512_lzcnt_epi32(__m512i __A) |
|
_mm512_mask_lzcnt_epi32
__m512i _mm512_mask_lzcnt_epi32(__m512i __W, __mmask16 __U, __m512i __A) |
|
_mm512_maskz_lzcnt_epi32
__m512i _mm512_maskz_lzcnt_epi32(__mmask16 __U, __m512i __A) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512CD_512 | AVX10.1 or 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 or AVX512CD + 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_128 | Same as AVX512CD_128 |
More AVX10.1 instructions
- VPERMT2PS
- VPERMT2Q
- VPERMT2W
- VPERMW
- VPEXPANDB
- VPEXPANDD
- VPEXPANDQ
- VPEXPANDW
- VPEXTRB
- VPEXTRD
- VPEXTRQ
- VPEXTRW
- VPGATHERDD
- VPGATHERDQ
- VPGATHERQD
- VPGATHERQQ
- VPINSRB
- VPINSRD
- VPINSRQ
- VPINSRW
- VPLZCNTQ
- VPMADD52HUQ
- VPMADD52LUQ
- VPMADDUBSW
- VPMADDWD
- VPMAXSB
- VPMAXSD
- VPMAXSQ
- VPMAXSW
- VPMAXUB
- VPMAXUD
- VPMAXUQ
- VPMAXUW
- VPMINSB
- VPMINSD
- VPMINSQ
- VPMINSW
- VPMINUB
- VPMINUD
- VPMINUQ
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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-562 (VPLZCNTD/
Q) - 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.