Instruction
VPANDQ
Computes the bitwise AND of two vectors, masked at quadword granularity.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPANDQ is VPANDD with quadwords: the bitwise AND of
two 128-, 256- or 512-bit values, whose write mask selects quadwords
and whose memory operand may be one quadword repeated to every element
({1to8} at 512 bits). The VPANDD page covers what the EVEX forms add
to the VEX VPAND and how the compilers choose between
the names; without a mask or a broadcast the two give the same bits.
On Zen 5, vpandq zmm7{k7}, zmm12, qword bcst [mem], with 1 in memory
and E3h in the low byte of K7, kept bit 0 of quadwords 0, 1, 5, 6 and 7
and cleared the rest of them, leaving quadwords 2 to 4 of ZMM7 as they
were: a test of the low bit that touches only the elements a mask
selects.
Quadword constants
A mask the width of a quadword is the usual reason for the Q:
- Low halves.
q[i] & 0xffffffffoverlong longarrays becomes VPANDQ against a broadcast constant in GCC 14 at -O2 with-march=x86-64-v4, one instruction per eight elements. - Bit fields. VPMULTISHIFTQB moves fields of each quadword into bytes, and VPANDQ with 1Fh in every byte clears what lies above a 5-bit field.
- 256-bit intrinsics. With
-march=x86-64-v4GCC compiles_mm256_and_si256tovpandq ymm0, ymm0, ymm1, as the VPAND page notes, where Clang 23 emits VANDPS.
Unmasked, the name need not match the data. Clang 23 with
-mavx512f swaps them: b[i] & 0xff over int arrays becomes
VPANDQ and q[i] & 0xffffffff over long long arrays VPANDD, the
reverse of GCC, with the same bits either way.
AMD’s Zen 5 latency spreadsheet gives the EVEX row of VPANDQ 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 |
|---|---|---|
VPANDQ zmm {k}{z}, zmm, zmm
VPANDQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512 | EVEX.512.66.0F.W1 DB /r | AVX10.1 or AVX512F |
VPANDQ zmm {k}{z}, zmm, m512/m64bcst
VPANDQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512 | EVEX.512.66.0F.W1 DB /r | AVX10.1 or AVX512F |
VPANDQ xmm {k}{z}, xmm, xmm
VPANDQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512 | EVEX.128.66.0F.W1 DB /r | AVX10.1 or AVX512F + AVX512VL |
VPANDQ xmm {k}{z}, xmm, m128/m64bcst
VPANDQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512 | EVEX.128.66.0F.W1 DB /r | AVX10.1 or AVX512F + AVX512VL |
VPANDQ ymm {k}{z}, ymm, ymm
VPANDQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512 | EVEX.256.66.0F.W1 DB /r | AVX10.1 or AVX512F + AVX512VL |
VPANDQ ymm {k}{z}, ymm, m256/m64bcst
VPANDQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512 | EVEX.256.66.0F.W1 DB /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m64bcst | xmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | xmm {k}{z}, xmm, m128/m64bcst | ymm {k}{z}, ymm, m256/m64bcst |
|---|---|---|---|---|---|
| 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 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 and xmm3. Result quadwords 1 to 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 // 64):
if k1[i]:
zmm1.q[i] = zmm2.q[i] & src3.q[i]
elif zeroing:
zmm1.q[i] = 0
# else: zmm1.q[i] keeps its value
# m64bcst: src3.q[i] is the m64 for every i
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPANDQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPANDQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPANDQ zmm {k}{z}, zmm, zmm/m512/m64bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | 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 VPANDQ, 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_epi64
__m128i _mm_mask_and_epi64(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_mask_and_pd
__m128d _mm_mask_and_pd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B) |
|
_mm_maskz_and_epi64
__m128i _mm_maskz_and_epi64(__mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_and_pd
__m128d _mm_maskz_and_pd(__mmask8 __U, __m128d __A, __m128d __B) |
|
_mm256_mask_and_epi64
__m256i _mm256_mask_and_epi64(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_mask_and_pd
__m256d _mm256_mask_and_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256d __B) |
|
_mm256_maskz_and_epi64
__m256i _mm256_maskz_and_epi64(__mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_and_pd
__m256d _mm256_maskz_and_pd(__mmask8 __U, __m256d __A, __m256d __B) |
|
_mm512_and_epi64
__m512i _mm512_and_epi64(__m512i __a, __m512i __b) |
|
_mm512_and_pd
__m512d _mm512_and_pd(__m512d __A, __m512d __B) |
|
_mm512_and_si512
__m512i _mm512_and_si512(__m512i __a, __m512i __b) |
|
_mm512_mask_and_epi64
__m512i _mm512_mask_and_epi64(__m512i __src, __mmask8 __k, __m512i __a, __m512i __b) |
|
_mm512_mask_and_pd
__m512d _mm512_mask_and_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512d __B) |
|
_mm512_maskz_and_epi64
__m512i _mm512_maskz_and_epi64(__mmask8 __k, __m512i __a, __m512i __b) |
|
_mm512_maskz_and_pd
__m512d _mm512_maskz_and_pd(__mmask8 __U, __m512d __A, __m512d __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
- VPABSB
- VPABSD
- VPABSQ
- VPABSW
- VPACKSSDW
- VPACKSSWB
- VPACKUSDW
- VPACKUSWB
- VPADDB
- VPADDD
- VPADDQ
- VPADDSB
- VPADDSW
- VPADDUSB
- VPADDUSW
- VPADDW
- VPALIGNR
- VPANDD
- VPANDND
- VPANDNQ
- VPAVGB
- VPAVGW
- VPBLENDMB
- VPBLENDMD
- VPBLENDMQ
- VPBLENDMW
- VPBROADCASTB
- VPBROADCASTD
- VPBROADCASTMB2Q
- VPBROADCASTMW2D
- VPBROADCASTQ
- VPBROADCASTW
- VPCLMULQDQ
- VPCMPB
- VPCMPD
- VPCMPEQB
- VPCMPEQD
- VPCMPEQQ
- VPCMPEQW
- VPCMPGTB
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.