Instruction
VPANDD
Computes the bitwise AND of two vectors, masked at doubleword granularity.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPANDD is the EVEX form of VPAND: the bitwise AND of two 128-, 256- or 512-bit values, with a write mask that selects doublewords. The AND itself knows no elements; the D names only the mask and the broadcast. VPANDQ is the same with quadwords, and without a mask or a broadcast the two give the same bits. What the EVEX form adds to VPAND:
- Masking. On Zen 5,
vpandd ymm0{k3}, ymm31, [mem]with EBh in the low byte of K3 wrote the AND to doublewords 0, 1, 3, 5, 6 and 7, kept 2 and 4 of YMM0 and cleared the bits from 256 up. With{z},vpandd ymm14{k3}{z}, ymm8, ymm29set doublewords 2 and 4 to 0. - Broadcast. The memory operand may be one doubleword repeated to
every element,
{1to16}at 512 bits: GCC 14 compiles_mm512_and_epi32(x, _mm512_set1_epi32(*p))tovpandd zmm0, zmm0, dword ptr [rdi]{1to16}, while Clang 23 broadcasts the value into a register first. - Registers 16 to 31 and ZMM registers, which VEX cannot name.
Which name the compilers pick
GCC 14 at -O2 follows the C type. With -march=x86-64-v4,
a[i] = b[i] & c[i] over int arrays becomes VPANDD on zmm registers
and over long long arrays VPANDQ; _mm512_and_si512 is VPANDD, and
the masked _mm512_mask_and_epi32 and _mm512_maskz_and_epi32 are
VPANDD with a merging or zeroing mask. Clang 23 picks by encoding
instead. With -mavx512f it emits VPANDD for the int loop and the
masked intrinsics but VPANDQ for _mm512_and_si512; with
-march=x86-64-v4, whose AVX512DQ brings an EVEX
VANDPS, it uses VANDPS for all of them (on ymm
registers in the loop), masked ones included, since a masked VANDPS
selects the same 32-bit elements.
AMD’s Zen 5 latency spreadsheet gives the EVEX row of VPANDD what it gives VPAND: one cycle and four per cycle on any of the four vector pipes. Zen 5’s 6 recorded cases cover the register and memory forms, broadcast included, at all three widths.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPANDD zmm {k}{z}, zmm, zmm
VPANDD_ZMMu32_MASKmskw_ZMMu32_ZMMu32_AVX512 | EVEX.512.66.0F.W0 DB /r | AVX10.1 or AVX512F |
VPANDD zmm {k}{z}, zmm, m512/m32bcst
VPANDD_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512 | EVEX.512.66.0F.W0 DB /r | AVX10.1 or AVX512F |
VPANDD xmm {k}{z}, xmm, xmm
VPANDD_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512 | EVEX.128.66.0F.W0 DB /r | AVX10.1 or AVX512F + AVX512VL |
VPANDD xmm {k}{z}, xmm, m128/m32bcst
VPANDD_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512 | EVEX.128.66.0F.W0 DB /r | AVX10.1 or AVX512F + AVX512VL |
VPANDD ymm {k}{z}, ymm, ymm
VPANDD_YMMu32_MASKmskw_YMMu32_YMMu32_AVX512 | EVEX.256.66.0F.W0 DB /r | AVX10.1 or AVX512F + AVX512VL |
VPANDD ymm {k}{z}, ymm, m256/m32bcst
VPANDD_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512 | EVEX.256.66.0F.W0 DB /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m32bcst | xmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | xmm {k}{z}, xmm, m128/m32bcst | ymm {k}{z}, ymm, m256/m32bcst |
|---|---|---|---|---|---|
| Skylake-SP, Ice Lake | 1 / 0.5p05 | 8 / 0.5p05 | 1 / 0.33p015 | 7 / 0.5p015 | 8 / 0.5p015 |
| Sapphire Rapids | 1 / 0.5p05 | 9 / 0.5p05 | 1 / 0.33p015 | 8 / 0.33p015 | 9 / 0.33p015 |
| Zen 4 | 1 / 0.5FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 8 / 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.
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 and xmm3. Result doublewords 3 to 0: a3&b3, unchanged (bit 2 of k1 is 0), a1&b1, a0&b0.
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] = zmm2.d[i] & src3.d[i]
elif zeroing:
zmm1.d[i] = 0
# else: zmm1.d[i] keeps its value
# m32bcst: src3.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 |
|---|---|---|
VPANDD xmm {k}{z}, xmm, xmm/m128/m32bcst VPANDD ymm {k}{z}, ymm, ymm/m256/m32bcst VPANDD zmm {k}{z}, zmm, zmm/m512/m32bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
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 VPANDD, 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_mask_and_epi32
__m128i _mm_mask_and_epi32(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_mask_and_ps
__m128 _mm_mask_and_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B) |
|
_mm_maskz_and_epi32
__m128i _mm_maskz_and_epi32(__mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_and_ps
__m128 _mm_maskz_and_ps(__mmask8 __U, __m128 __A, __m128 __B) |
|
_mm256_mask_and_epi32
__m256i _mm256_mask_and_epi32(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_mask_and_ps
__m256 _mm256_mask_and_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B) |
|
_mm256_maskz_and_epi32
__m256i _mm256_maskz_and_epi32(__mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_and_ps
__m256 _mm256_maskz_and_ps(__mmask8 __U, __m256 __A, __m256 __B) |
|
_mm512_and_epi32
__m512i _mm512_and_epi32(__m512i __a, __m512i __b) |
|
_mm512_and_ps
__m512 _mm512_and_ps(__m512 __A, __m512 __B) |
|
_mm512_mask_and_epi32
__m512i _mm512_mask_and_epi32(__m512i __src, __mmask16 __k, __m512i __a, __m512i __b) |
|
_mm512_mask_and_ps
__m512 _mm512_mask_and_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_maskz_and_epi32
__m512i _mm512_maskz_and_epi32(__mmask16 __k, __m512i __a, __m512i __b) |
|
_mm512_maskz_and_ps
__m512 _mm512_maskz_and_ps(__mmask16 __U, __m512 __A, __m512 __B) |
|
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 |
|---|---|---|
AVX512F_512 | AVX10.1 or AVX512F | 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 |
AVX512F_128 | AVX10.1 or AVX512F + 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 |
AVX512F_256 | Same as AVX512F_128 | Same as AVX512F_128 |
More AVX10.1 instructions
- VMULSS
- VORPD
- VORPS
- VPABSB
- VPABSD
- VPABSQ
- VPABSW
- VPACKSSDW
- VPACKSSWB
- VPACKUSDW
- VPACKUSWB
- VPADDB
- VPADDD
- VPADDQ
- VPADDSB
- VPADDSW
- VPADDUSB
- VPADDUSW
- VPADDW
- VPALIGNR
- VPANDND
- VPANDNQ
- VPANDQ
- VPAVGB
- VPAVGW
- VPBLENDMB
- VPBLENDMD
- VPBLENDMQ
- VPBLENDMW
- VPBROADCASTB
- VPBROADCASTD
- VPBROADCASTMB2Q
- VPBROADCASTMW2D
- VPBROADCASTQ
- VPBROADCASTW
- VPCLMULQDQ
- VPCMPB
- VPCMPD
- VPCMPEQB
- VPCMPEQD
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 2B, page 4-220 (PAND)
- 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.