Extensions
Forms
1 (1 VEX)
Data
Intel XED v2026.08.23

KANDW ANDs the low 16 bits of two mask registers into a third and clears bits 63:16 of the result. Bits above 15 of the sources play no part: the cases recorded on Zen 5 give sources whose upper bits are all ones and still get 16-bit results. Since the destination is a separate operand, one mask can be combined with several others without being copied first.

KANDW belongs to AVX-512F, with the other word-sized mask logic: KORW, KXORW, KXNORW, KNOTW and KANDNW, which ANDs the inverted first source with the second. The byte form, KANDB, needs AVX512DQ, and KANDD and KANDQ need AVX512BW.

Two conditions at once

Intel’s optimization manual uses KANDW to join two compares into the mask of a loop body that runs where x > 0 && (x & 3) == 3 (Section 17.2.4). Compilers mostly find something shorter. With GCC 14 and Clang 23 at -O2 and -mavx512f, the AND of two compare masks used as a write mask became:

  • in both compilers, for compares of floats, the second compare run under the first one’s mask, as in vcmpps k1{k1}, zmm0, zmm2, 17: a masked compare writes 0 for every element its mask excludes, which is the AND;
  • in Clang, for a > b && a > c on signed doublewords, one VPMAXSD and one compare, since a is greater than both exactly when it is greater than their maximum.

KANDW itself shows up when the operands are masks already: GCC compiles _mm512_kand(a, b) on two __mmask16 arguments to two KMOVW instructions, KANDW and a KMOVW back to EAX, while Clang ANDs the arguments in general-purpose registers.

The instruction table of AMD’s Zen 5 guide lists KANDW, like KORW, KXORW, KNOTW and KANDNW, as one macro-op with a latency of one cycle.

In the optimization guide

What the optimization guide says about KANDW, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Vectors

  • Masks and masked memory access: Mask logic such as KANDW combines conditions, while moving a mask from a general register costs two macro-ops on Zen 4 and Zen 5.

Forms

Every encoding of KANDW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
KANDW k, k, k KANDW_MASKmskw_MASKmskw_MASKmskw_AVX512VEX.L1.NP.0F.W0 41 /rAVX10.1 or AVX512F

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, k
Skylake-SP, Ice Lake, Sapphire Rapids1 / 1p0
Zen 41 / 0.5FP2 FP3

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

k1.w[0] = k2.w[0] & k3.w[0]
# bits 63:16 of k1 are cleared

Run on AMD Zen 5 (EPYC 9645): 11 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
KANDW k, k, k
kexplicitwrite
kexplicitread
kexplicitread

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-K20

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to KANDW, 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
_mm512_kand __mmask16 _mm512_kand(__mmask16 __A, __mmask16 __B)

KANDW k, k, k VEX.L1 -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_KOPW

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

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 2A, page 3-516 (KANDW/KANDB/KANDQ/KANDD)
  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.