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

VPTESTNMQ sets bit i of its destination mask when quadwords i of its two sources AND to zero: 2, 4 or 8 bits for the XMM, YMM and ZMM forms. It is the quadword form of VPTESTNMD, whose page covers the masking it shares with the compares, and the complement of VPTESTMQ. It came with AVX512F and takes a 64-bit broadcast. A register tested against itself marks the zero quadwords; against a constant, the elements in which those bits are all clear.

Recorded on Zen 5

  • Two zero ANDs. vptestnmq k6{k3}, zmm24, zmm3 gave 42h: 8000000000000000h against 1 and 0 against 8000000000000000h AND to zero, while F against 1 and 8000000000000000h against itself do not. The register and memory forms gave the same 42h, and the other 56 bits of K6 and K5 were cleared.
  • Nothing selected. In vptestnmq k5{k1}, xmm17, xmm30 the low two bits of K1 were clear, and K5 became 0.

In compiled code

At -O2 with -march=x86-64-v4, (q[i] & 7) == 0 ? q[i] : 0 over int64_t is VPTESTNMQ and a zero-masked move in GCC 14 and Clang 23. Clang tests q[i] against a vector of sevens; GCC first ANDs with VPANDQ and tests the result against itself. A test whether a whole vector is zero, written as _mm512_testn_epi64_mask(a, a) == 0xff, is VPTESTNMQ, KMOVB and a compare of AL with FFh in GCC, while Clang turns it into VPTESTMD and KORTESTW.

AMD’s Zen 5 latency spreadsheet gives one macro-op on pipe FP1 or FP2 and 3, 4 and 6 cycles for XMM, YMM and ZMM sources, with a second macro-op for a memory operand.

Forms

Every encoding of VPTESTNMQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPTESTNMQ k {k}, zmm, zmm VPTESTNMQ_MASKmskw_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.F3.0F38.W1 27 /rAVX10.1 or AVX512F
VPTESTNMQ k {k}, zmm, m512/m64bcst VPTESTNMQ_MASKmskw_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.F3.0F38.W1 27 /rAVX10.1 or AVX512F
VPTESTNMQ k {k}, xmm, xmm VPTESTNMQ_MASKmskw_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.F3.0F38.W1 27 /rAVX10.1 or AVX512F + AVX512VL
VPTESTNMQ k {k}, xmm, m128/m64bcst VPTESTNMQ_MASKmskw_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.F3.0F38.W1 27 /rAVX10.1 or AVX512F + AVX512VL
VPTESTNMQ k {k}, ymm, ymm VPTESTNMQ_MASKmskw_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.F3.0F38.W1 27 /rAVX10.1 or AVX512F + AVX512VL
VPTESTNMQ k {k}, ymm, m256/m64bcst VPTESTNMQ_MASKmskw_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.F3.0F38.W1 27 /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.
Modelk {k}, zmm, zmmno maskk {k}, zmm, zmmwith a maskk {k}, zmm, m512/m64bcst
k {k}, ymm, m256/m64bcst
k {k}, xmm, xmmno maskk {k}, xmm, xmmwith a maskk {k}, xmm, m128/m64bcstk {k}, ymm, ymm
Skylake-SP, Ice Lake4 / 1p54 / 1p511 / 1p54 / 1p54 / 1p510 / 1p54 / 1p5
Sapphire Rapids3 / 1p53 / 1p53 / 1p53 / 1p53 / 1p53 / 1p53 / 1p5
Zen 41 / 0.5FP0 FP1 FP2 FP35 / 2.5FP0 FP18 / 0.5FP0 FP1 FP2 FP31 / 0.25FP0 FP1 FP2 FP33 / 1.5FP0 FP18 / 0.5FP0 FP1 FP2 FP34 / 2FP0 FP1

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.

To a mask: each quadword of the sources sets one bit of k1, bit i for quadword i.
VPTESTNMQ: a bit of k1 per elementBit i of k1 comes from quadword i of xmm2 and xmm3. Result bits 1 to 0: r1, r0.01xmm2a11k2r0r1k101xmm3or m128b

Where a bit of the write mask k2 is 0, the result bit is 0. Every quadword works alike: 2, 4 and 8 quadwords in the xmm, ymm and zmm forms. With m64bcst, one quadword from memory stands for every element of the last source.

Bit i of k1 comes from quadword i of xmm2 and xmm3. Result bits 1 to 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 // 64):
    a = zmm2.q[i]
    b = src3.q[i]
    k1[i] = k2[i] and a & b == 0
# m64bcst: src3.q[i] is the m64 for every i
# the other bits of k1 are cleared

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
VPTESTNMQ k {k}, xmm, xmm/m128/m64bcst VPTESTNMQ k {k}, ymm, ymm/m256/m64bcst VPTESTNMQ k {k}, zmm, zmm/m512/m64bcst
kexplicitwrite (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 VPTESTNMQ, 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_testn_epi64_mask __mmask8 _mm_testn_epi64_mask(__m128i __A, __m128i __B)

VPTESTNMQ k, xmm, xmm EVEX.128 -mavx512vl

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

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

_mm256_testn_epi64_mask __mmask8 _mm256_testn_epi64_mask(__m256i __A, __m256i __B)

VPTESTNMQ k, ymm, ymm EVEX.256 -mavx512vl

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

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

_mm512_testn_epi64_mask __mmask8 _mm512_testn_epi64_mask(__m512i __A, __m512i __B)

VPTESTNMQ k, zmm, zmm EVEX.512 -mavx512f

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

VPTESTNMQ k, zmm, zmm EVEX.512 -mavx512f

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 2C, page 5-657 (VPTESTNMB/W/D/Q)
  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.