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

VPTESTMD ANDs each pair of doublewords and sets a mask bit where the AND has any bit set; VPTESTNMD sets it where the AND is zero. Where PTEST folds a whole register into ZF and CF, these keep one answer per element in a mask register, with the masking of the compares: an element the write mask leaves out gets 0, and the bits above the element count are cleared. The doubleword and quadword forms are AVX-512F; VPTESTMB and VPTESTMW need AVX512BW.

Three common tests

  • Nonzero elements. VPTESTMD of a register with itself marks the nonzero elements and VPTESTNMD the zero ones, a compare with zero that needs no zeroed register. GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 both compile _mm512_cmpeq_epi32_mask(a, zero) to vptestnmd k0, zmm0, zmm0; for not equal, Clang emits VPTESTMD of a with itself, while GCC clears a register and uses VPCMPD with predicate 4. Clang also vectorizes o[i] = a[i] ? 7 : o[i] with VPTESTNMD and a VPBLENDMD.
  • Flag bits. Against a broadcast constant, the test picks one bit or a set of bits out of every element; Clang folds the constant into a {1to16} operand. For (a & b) != 0 on vectors of int, Clang emits one VPTESTMD, GCC a VPANDD and a VPCMPD.
  • Any element at all. VPTESTMD and then KORTESTW of the mask with itself sets ZF when no element passed, which a branch can test. Intel’s optimization manual does this in its histogram loop (Section 17.16.1, Example 17-24): VPTESTMD of the VPCONFLICTD result with itself and KORTESTW skip the merging of repeated indices when there are none.

The same manual makes the bitmask of a sparse matrix with VPTESTMB, a bit per nonzero byte, and packs the nonzero bytes with VPCOMPRESS (Section 20.18). AMD’s Zen 5 guide lists VPTESTMD with the latencies of VPCMPD, 3, 4 and 6 cycles for XMM, YMM and ZMM.

Forms

Every encoding of VPTESTMD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPTESTMD k {k}, zmm, zmm VPTESTMD_MASKmskw_MASKmskw_ZMMu32_ZMMu32_AVX512EVEX.512.66.0F38.W0 27 /rAVX10.1 or AVX512F
VPTESTMD k {k}, zmm, m512/m32bcst VPTESTMD_MASKmskw_MASKmskw_ZMMu32_MEMu32_AVX512EVEX.512.66.0F38.W0 27 /rAVX10.1 or AVX512F
VPTESTMD k {k}, xmm, xmm VPTESTMD_MASKmskw_MASKmskw_XMMu32_XMMu32_AVX512EVEX.128.66.0F38.W0 27 /rAVX10.1 or AVX512F + AVX512VL
VPTESTMD k {k}, xmm, m128/m32bcst VPTESTMD_MASKmskw_MASKmskw_XMMu32_MEMu32_AVX512EVEX.128.66.0F38.W0 27 /rAVX10.1 or AVX512F + AVX512VL
VPTESTMD k {k}, ymm, ymm VPTESTMD_MASKmskw_MASKmskw_YMMu32_YMMu32_AVX512EVEX.256.66.0F38.W0 27 /rAVX10.1 or AVX512F + AVX512VL
VPTESTMD k {k}, ymm, m256/m32bcst VPTESTMD_MASKmskw_MASKmskw_YMMu32_MEMu32_AVX512EVEX.256.66.0F38.W0 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/m32bcst
k {k}, ymm, m256/m32bcst
k {k}, xmm, xmmno maskk {k}, xmm, xmmwith a maskk {k}, xmm, m128/m32bcstk {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.251FP0 FP1 FP2 FP33 / 1.52FP0 FP18 / 0.5FP0 FP1 FP2 FP34 / 23FP0 FP1
  1. Zen 4 model: AMD's spreadsheets give latency 3 for Zen 4 and Zen 5 (AMD 57647, row 3081; AMD 58455, row 397).
  2. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 3081; AMD 58455, row 397).
  3. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 3083; AMD 58455, row 399).

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 doubleword of the sources sets one bit of k1, bit i for doubleword i.
VPTESTMD: a bit of k1 per elementBit i of k1 comes from doubleword i of xmm2 and xmm3. Result bits 3 to 0: r3, 0 (bit 2 of k2 is 0), r1, r0.0123xmm2a1110k2r0r1r30k10123xmm3or m128b

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

Bit i of k1 comes from doubleword i of xmm2 and xmm3. Result bits 3 to 0: r3, 0 (bit 2 of k2 is 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 // 32):
    a = zmm2.d[i]
    b = src3.d[i]
    k1[i] = k2[i] and a & b != 0
# m32bcst: src3.d[i] is the m32 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
VPTESTMD k {k}, xmm, xmm/m128/m32bcst VPTESTMD k {k}, ymm, ymm/m256/m32bcst VPTESTMD k {k}, zmm, zmm/m512/m32bcst
kexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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 VPTESTMD, 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_test_epi32_mask __mmask8 _mm_test_epi32_mask(__m128i __A, __m128i __B)

VPTESTMD k, xmm, xmm EVEX.128 -mavx512vl

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

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

_mm256_test_epi32_mask __mmask8 _mm256_test_epi32_mask(__m256i __A, __m256i __B)

VPTESTMD k, ymm, ymm EVEX.256 -mavx512vl

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

VPTESTMD k, ymm, ymm EVEX.256 -mavx512vl

_mm512_test_epi32_mask __mmask16 _mm512_test_epi32_mask(__m512i __A, __m512i __B)

VPTESTMD k, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_test_epi32_mask __mmask16 _mm512_mask_test_epi32_mask(__mmask16 __U, __m512i __A, __m512i __B)

VPTESTMD 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-654 (VPTESTMB/VPTESTMW/VPTESTMD/VPTESTMQ)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 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.