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

VPANDNQ is the EVEX form of VPANDN with a write mask that selects quadwords: NOT of the first source AND the second, over 128, 256 or 512 bits, with a memory operand that may be one quadword repeated, {1to8} at 512 bits. VPANDND is the same with doublewords and covers the zeroing idiom and how the compilers choose between the two names; unmasked they give the same bits.

Recorded on Zen 5

  • {evex} vpandnq xmm1, xmm2, xmm3 with 0 and 1 in the quadwords of XMM2 and 1 and 0 in those of XMM3 gave 1 and 0: only XMM2 was inverted.
  • vpandnq zmm7{k6}, zmm12, qword bcst [mem] with a broadcast 0 wrote zeros only to quadwords 2, 5 and 7, the ones A4h selects, and left the other five of ZMM7 alone: a masked VPANDNQ against zero clears chosen elements.

In compiled code

GCC 14 at -O2 with -march=x86-64-v4 compiles _mm512_andnot_epi64 and its masked forms to VPANDNQ, and also the AVX2 intrinsic _mm256_andnot_si256, as an EVEX vpandnq ymm0, ymm0, ymm1 where the VEX VPANDN would do; with -mavx512f, which lacks AVX512VL, it emits VPANDN there. When the inverted operand is the broadcast one, _mm512_andnot_epi64(_mm512_set1_epi64(*p), a), the memory operand cannot be the first source, and GCC emits vpternlogq zmm0, zmm0, qword ptr [rdi]{1to8}, 0x44 instead, while Clang 23 inverts the value with VPTERNLOGQ, broadcasts it and ANDs with VPANDQ.

Clang 23 with -mavx512f uses VPANDNQ for every unmasked AND-NOT intrinsic, whatever its element size, and for qd[i] = qb[i] & ~qc[i] over long long arrays; with -march=x86-64-v4 it uses VANDNPS, or VANDNPD under a quadword mask.

AMD’s Zen 5 latency spreadsheet gives VPANDNQ 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

Every encoding of VPANDNQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPANDNQ zmm {k}{z}, zmm, zmm VPANDNQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.66.0F.W1 DF /rAVX10.1 or AVX512F
VPANDNQ zmm {k}{z}, zmm, m512/m64bcst VPANDNQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F.W1 DF /rAVX10.1 or AVX512F
VPANDNQ xmm {k}{z}, xmm, xmm VPANDNQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F.W1 DF /rAVX10.1 or AVX512F + AVX512VL
VPANDNQ xmm {k}{z}, xmm, m128/m64bcst VPANDNQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F.W1 DF /rAVX10.1 or AVX512F + AVX512VL
VPANDNQ ymm {k}{z}, ymm, ymm VPANDNQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.66.0F.W1 DF /rAVX10.1 or AVX512F + AVX512VL
VPANDNQ ymm {k}{z}, ymm, m256/m64bcst VPANDNQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F.W1 DF /rAVX10.1 or AVX512F + 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}, zmm, zmmzmm {k}{z}, zmm, m512/m64bcstxmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
xmm {k}{z}, xmm, m128/m64bcstymm {k}{z}, ymm, m256/m64bcst
Skylake-SP, Ice Lake1 / 0.5p058 / 0.5p051 / 0.33p0157 / 0.5p0158 / 0.5p015
Sapphire Rapids1 / 0.5p059 / 0.5p051 / 0.33p0158 / 0.33p0159 / 0.33p015
Zen 41 / 0.5FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP31 / 0.25FP0 FP1 FP2 FP38 / 0.5FP0 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.
VPANDNQ: element by elementResult quadword i comes from quadword i of xmm2 and xmm3. Result quadwords 1 to 0: ~a1&b1, ~a0&b0.01xmm2a11k1~a0&b0~a1&b1xmm101xmm3or m128b

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 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
VPANDNQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPANDNQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPANDNQ zmm {k}{z}, zmm, zmm/m512/m64bcst
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
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 VPANDNQ, 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_mask_andnot_epi64 __m128i _mm_mask_andnot_epi64(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B)

VPANDNQ xmm {k}, xmm, xmm EVEX.128 -mavx512vl

_mm_mask_andnot_pd __m128d _mm_mask_andnot_pd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B)

VPANDNQ xmm {k}, xmm, xmm EVEX.128 -mavx512vl -mavx512dq

_mm_maskz_andnot_epi64 __m128i _mm_maskz_andnot_epi64(__mmask8 __U, __m128i __A, __m128i __B)

VPANDNQ xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl

_mm_maskz_andnot_pd __m128d _mm_maskz_andnot_pd(__mmask8 __U, __m128d __A, __m128d __B)

VPANDNQ xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl -mavx512dq

_mm256_mask_andnot_epi64 __m256i _mm256_mask_andnot_epi64(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B)

VPANDNQ ymm {k}, ymm, ymm EVEX.256 -mavx512vl

_mm256_mask_andnot_pd __m256d _mm256_mask_andnot_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256d __B)

VPANDNQ ymm {k}, ymm, ymm EVEX.256 -mavx512vl -mavx512dq

_mm256_maskz_andnot_epi64 __m256i _mm256_maskz_andnot_epi64(__mmask8 __U, __m256i __A, __m256i __B)

VPANDNQ ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl

_mm256_maskz_andnot_pd __m256d _mm256_maskz_andnot_pd(__mmask8 __U, __m256d __A, __m256d __B)

VPANDNQ ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl -mavx512dq

_mm512_andnot_epi64 __m512i _mm512_andnot_epi64(__m512i __A, __m512i __B)

VPANDNQ zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_andnot_pd __m512d _mm512_andnot_pd(__m512d __A, __m512d __B)

VPANDNQ zmm, zmm, zmm EVEX.512 -mavx512dq

_mm512_andnot_si512 __m512i _mm512_andnot_si512(__m512i __A, __m512i __B)

VPANDNQ zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_andnot_epi64 __m512i _mm512_mask_andnot_epi64(__m512i __W, __mmask8 __U, __m512i __A, __m512i __B)

VPANDNQ zmm {k}, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_andnot_pd __m512d _mm512_mask_andnot_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512d __B)

VPANDNQ zmm {k}, zmm, zmm EVEX.512 -mavx512dq

_mm512_maskz_andnot_epi64 __m512i _mm512_maskz_andnot_epi64(__mmask8 __U, __m512i __A, __m512i __B)

VPANDNQ zmm {k}{z}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_andnot_pd __m512d _mm512_maskz_andnot_pd(__mmask8 __U, __m512d __A, __m512d __B)

VPANDNQ zmm {k}{z}, zmm, zmm EVEX.512 -mavx512dq

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
AVX512F_512

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

or

AVX512F
CPUID.(EAX=07H,ECX=0):EBX[16] 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
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
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
AVX512F_256
Same as AVX512F_128Same as AVX512F_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 2B, page 4-223 (PANDN)
  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.