x86-64.net

Instruction

KXORD

Computes the bitwise XOR of two 32-bit masks.

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

KXORD XORs the low 32 bits of two mask registers into a third and clears bits 63:32: a bit is 1 where the two sources differ. It is the AVX512BW form of KXORW for masks of 32 elements, one per word of a ZMM register or per byte of a YMM register. KXORW’s page explains what the XOR of two masks selects, and why a register XORed with itself, though it gives zero, is not on either vendor’s list of dependency-breaking idioms. KXORQ is the 64-bit form and KXNORD the inverse.

Recorded on Zen 5

  • The upper halves do not count. kxord k1, k2, k3 with B96B123400000000h and FFFFFFFF00000000h gave 0, and so did 4E734E3A55555555h against FFFFFFFF55555555h, whose low halves match.
  • One register twice. kxord k5, k6, k6 and kxord k7, k7, k7 wrote 0, whatever the register held.
  • Random bits. FFFFFFFFCCB698ECh against 665DC2E7h gave AAEB5A0Bh, with bits 63:32 cleared.
  • K0 is a register here. kxord k6, k7, k0 read K0, and kxord k0, k4, k5 wrote 17A255DAh to it.

In compiled code

With GCC 14 and Clang 23 at -O2 and -march=x86-64-v4, the words that equal exactly one of b and c, _mm512_cmpeq_epi16_mask(a, b) ^ _mm512_cmpeq_epi16_mask(a, c) used as the zero mask of a VMOVDQU16, are one KXORD in both, after two VPCMPW with predicate 0 in GCC and two VPCMPEQW in Clang; the same on the bytes of YMM registers is KXORD as well. When the XOR only decides whether the two masks differ, Clang keeps KXORD and tests it with KORTESTD, while GCC moves both masks out with KMOVD and compares them with CMP. m ^ (m << 1) on a word compare, which marks where the condition changes, is KSHIFTLD and KXORD in both. _kxor_mask32 of two arguments is KMOVD twice, KXORD and a KMOVD back in GCC, and XOR on EAX in Clang.

AMD’s Zen 5 latency spreadsheet gives KXORD one cycle and two per cycle on pipes FP0 and FP3, as KXORW.

Forms

Every encoding of KXORD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
KXORD k, k, k KXORD_MASKmskw_MASKmskw_MASKmskw_AVX512VEX.L1.66.0F.W1 47 /rAVX10.1 or AVX512BW

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.d[0] = k2.d[0] ^ k3.d[0]
# bits 63:32 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
KXORD 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 KXORD, 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
_kxor_mask32 __mmask32 _kxor_mask32(__mmask32 __A, __mmask32 __B)

KXORD k, k, k VEX.L1 -mavx512bw

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
AVX512BW_KOPD

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

or

AVX512BW
CPUID.(EAX=07H,ECX=0):EBX[30] AVX512BW

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

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-531 (KXORW/KXORB/KXORQ/KXORD)
  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.