Extensions
Forms
10 (4 VEX, 6 EVEX)
Data
Intel XED v2026.08.23

VANDNPD inverts its first source and ANDs the result with the second: the VEX and EVEX form of ANDNPD, whose page covers the operation, while VANDNPS explains the operand order. The newer encodings write a separate destination, read memory at any alignment and zero the register above the vector length. The VEX forms need AVX, ymm included; the EVEX forms need AVX512DQ (with AVX512VL below 512 bits) or AVX10.1, and add a write mask per double and a second source of one broadcast double. Only the second source can be memory, so the inverted operand is always a register.

Recorded on Zen 5

With MXCSR at 1F80H, no case set a flag:

  • vandnpd xmm12, xmm6, xmmword ptr [mem], with 7FFFFFFFFFFFFFFFh and -0.0 in XMM6 and the smallest denormal in both doubles of memory, gave 0 and that denormal, and zeroed bits 511:128 of ZMM12.
  • vandnpd zmm1{k3}, zmm2, qword bcst [mem], with the same denormal broadcast, wrote it where k3 selected an element and ZMM2 held -0.0 (elements 5 and 7), 0 in the other selected ones, and kept elements 2 and 4 of ZMM1.

In compiled code

In our builds at -O2 over global double arrays with -march=x86-64-v3, GCC 14 compiles a[i] = b[i] < c[i] ? 0.0 : d[i] to VCMPLTPD and vandnpd ymm0, ymm0, ymmword ptr [...], the compare result being the inverted operand; Clang 23 inverts the compare to VCMPNLTPD and uses VANDPD. With -march=x86-64-v4 the compare writes a mask register and a masked move selects. For -fabs(b[i]), GCC clears the sign bits with VANDNPD of -0.0 and sets them again with VORPD; for copysign its VANDNPD of -0.0 keeps the magnitude, as VANDPD’s page shows. At -v4 each becomes one VPTERNLOGQ.

Clang spells _mm512_andnot_pd as VANDNPS but keeps VANDNPD where the elements matter: with a mask, and with a broadcast, as in vandnpd zmm0, zmm0, qword bcst [rdi] for _mm512_andnot_pd(x, _mm512_set1_pd(*p)), where GCC loads the double with VBROADCASTSD first.

AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows alike one macro-op with a latency of 1 cycle on pipes FP0 to FP3, four per cycle.

Forms

Every encoding of VANDNPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VANDNPD xmm, xmm, m128 VANDNPD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG 55 /rAVX
VANDNPD xmm, xmm, xmm VANDNPD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG 55 /rAVX
VANDNPD ymm, ymm, m256 VANDNPD_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG 55 /rAVX
VANDNPD ymm, ymm, ymm VANDNPD_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG 55 /rAVX
VANDNPD xmm {k}{z}, xmm, xmm VANDNPD_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F.W1 55 /rAVX10.1 or AVX512DQ + AVX512VL
VANDNPD xmm {k}{z}, xmm, m128/m64bcst VANDNPD_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F.W1 55 /rAVX10.1 or AVX512DQ + AVX512VL
VANDNPD ymm {k}{z}, ymm, ymm VANDNPD_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.66.0F.W1 55 /rAVX10.1 or AVX512DQ + AVX512VL
VANDNPD ymm {k}{z}, ymm, m256/m64bcst VANDNPD_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F.W1 55 /rAVX10.1 or AVX512DQ + AVX512VL
VANDNPD zmm {k}{z}, zmm, zmm VANDNPD_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.66.0F.W1 55 /rAVX10.1 or AVX512DQ
VANDNPD zmm {k}{z}, zmm, m512/m64bcst VANDNPD_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F.W1 55 /rAVX10.1 or AVX512DQ

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.
Modelxmm, xmm, m128
xmm {k}{z}, xmm, m128/m64bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m64bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmmzmm {k}{z}, zmm, m512/m64bcst
Sandy Bridge, Haswell7 / 1p51 / 1p58 / 1p51 / 1p5
Broadwell6 / 1p51 / 1p57 / 1p51 / 1p5
Skylake7 / 0.5p0151 / 0.33p0158 / 0.5p0151 / 0.33p015
Skylake-SP, Ice Lake7 / 0.5p0151 / 0.33p0158 / 0.5p0151 / 0.33p0151 / 0.5p058 / 0.5p05
Alder Lake8 / 0.33p0151 / 0.33p0159 / 0.33p0151 / 0.33p015
Sapphire Rapids8 / 0.33p0151 / 0.33p0159 / 0.33p0151 / 0.33p0151 / 0.5p059 / 0.5p05
Lunar Lake7 / 2V0 V1 V2 V31 / 0.25V0 V1 V2 V38 / 2.33V0 V1 V2 V31 / 0.25V0 V1 V2 V3
Piledriver7 / 1.5FPMAL2 / 0.5FPMAL FPU2 FPU37 / 1.5FPMAL2 / 1FPMAL FPU2 FPU3
Zen8 / 0.5FPU0 FPU1 FPU2 FPU31 / 0.25FPU0 FPU1 FPU2 FPU38 / 0.5FPU0 FPU1 FPU2 FPU31 / 0.5FPU0 FPU1 FPU2 FPU3
Zen 28 / 0.33FPU0 FPU1 FPU2 FPU31 / 0.25FPU0 FPU1 FPU2 FPU38 / 0.33FPU0 FPU1 FPU2 FPU31 / 0.25FPU0 FPU1 FPU2 FPU3
Zen 38 / 0.5FP0 FP1 FP2 FP31 / 0.25FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP31 / 0.25FP0 FP1 FP2 FP3
Zen 48 / 0.5FP0 FP1 FP2 FP31 / 0.25FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP31 / 0.25FP0 FP1 FP2 FP31 / 0.5FP0 FP1 FP2 FP38 / 0.5FP0 FP1 FP2 FP3
Jaguar6 / 1FPA FPM FPU0 FPU11 / 0.5FPA FPM FPU0 FPU16 / 2FPA FPM FPU0 FPU11 / 1FPA FPM FPU0 FPU1

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.
VANDNPD: 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 EVEX 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]:  # 1 without a write mask
        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): 10 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
VANDNPD xmm, xmm, xmm/m128 VANDNPD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VANDNPD xmm {k}{z}, xmm, xmm/m128/m64bcst VANDNPD ymm {k}{z}, ymm, ymm/m256/m64bcst VANDNPD 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.

VEX forms
avx-type-4
EVEX forms
AVX512-E4

Attributes

What else XED records about the forms. How to read.

EVEX forms
write masking
EVEX memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VANDNPD, 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
_mm256_andnot_pd __m256d _mm256_andnot_pd(__m256d __a, __m256d __b)

VANDNPD ymm, ymm, ymm VEX.256 -mavxClang emits the equivalent VANDNPS

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
AVX

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
AVX512DQ_128

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

or

AVX512DQ + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ
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
AVX512DQ_256
Same as AVX512DQ_128Same as AVX512DQ_128
AVX512DQ_512

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

or

AVX512DQ
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ

Same as AVX512DQ_128

More AVX instructions

All 253 AVX instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-63 (ANDNPD)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. 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.