Instruction
VPXORD
Computes the bitwise XOR of two vectors, masked at doubleword granularity.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPXORD is the EVEX form of VPXOR: the bitwise exclusive OR of two 128-, 256- or 512-bit values, with a write mask that selects doublewords and a memory operand that may be one doubleword repeated to every element. VPXORQ is the same with quadwords; unmasked, the two give the same bits. VPANDD shows what the EVEX forms add and how GCC 14 and Clang 23 choose among the names.
Zeroing
XOR of a register with itself gives zero, and the VPXOR page describes that idiom. EVEX matters for it in two ways:
- Registers 16 to 31 have no VEX encoding. When every lower
register is in use, GCC 14 at -O2 zeroes ZMM16 with
vpxord xmm16, xmm16, xmm16under-march=x86-64-v4, and both compilers withvpxord zmm16, zmm16, zmm16under-mavx512f, which lacks the AVX512VL needed for the shorter forms. - A mask makes the old value matter again. On Zen 5,
vpxord zmm5{k6}, zmm5, zmm5with 43A4h in the low 16 bits of K6 cleared doublewords 2, 5, 7, 8, 9 and 14 and kept the other ten.
Intel’s optimization manual breaks a false dependency with an unmasked
vpxord zmm3, zmm3, zmm3, which it calls a zero idiom (Section
2.4.1.2, Example 2-5), though its list of 512-bit zero idioms names
VPXOR (Section 3.5.1.7). AMD’s Zen 5 guide likewise lists VPXOR with
zmm operands among the zeroing idioms that take no cycle (Section
2.9.2); VPXOR has no 512-bit encoding, so both lists can only mean
the EVEX forms.
In compiled code
With -march=x86-64-v4, GCC uses VPXORD for a[i] = b[i] ^ c[i] over
int arrays and in the last steps of a vectorized XOR of 32-bit
values, where it folds the halves of a zmm register with
VEXTRACTI32X8 and
VEXTRACTI32X4, each followed by VPXORD. For a
test of two vectors for equality it emits VPXORD and a
VPTESTMQ of the result.
AMD’s Zen 5 latency spreadsheet gives the EVEX row of VPXORD one cycle and four per cycle on any of the four vector pipes. Zen 5’s 6 recorded cases cover the register and memory forms, broadcast included, at all three widths.
In the optimization guide
What the optimization guide says about VPXORD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Out of order
- Zeroing and dependency-breaking idioms: The vector registers have idioms of their own:
pxor,xorps,xorpd,pandn,andnps, the integer subtractionspsuband the comparisonspcmpgtof a register with itself, with their VEX and EVEX forms, which Intel counts for 512-bit registers only unmasked. sources differ
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPXORD zmm {k}{z}, zmm, zmm
VPXORD_ZMMu32_MASKmskw_ZMMu32_ZMMu32_AVX512 | EVEX.512.66.0F.W0 EF /r | AVX10.1 or AVX512F |
VPXORD zmm {k}{z}, zmm, m512/m32bcst
VPXORD_ZMMu32_MASKmskw_ZMMu32_MEMu32_AVX512 | EVEX.512.66.0F.W0 EF /r | AVX10.1 or AVX512F |
VPXORD xmm {k}{z}, xmm, xmm
VPXORD_XMMu32_MASKmskw_XMMu32_XMMu32_AVX512 | EVEX.128.66.0F.W0 EF /r | AVX10.1 or AVX512F + AVX512VL |
VPXORD xmm {k}{z}, xmm, m128/m32bcst
VPXORD_XMMu32_MASKmskw_XMMu32_MEMu32_AVX512 | EVEX.128.66.0F.W0 EF /r | AVX10.1 or AVX512F + AVX512VL |
VPXORD ymm {k}{z}, ymm, ymm
VPXORD_YMMu32_MASKmskw_YMMu32_YMMu32_AVX512 | EVEX.256.66.0F.W0 EF /r | AVX10.1 or AVX512F + AVX512VL |
VPXORD ymm {k}{z}, ymm, m256/m32bcst
VPXORD_YMMu32_MASKmskw_YMMu32_MEMu32_AVX512 | EVEX.256.66.0F.W0 EF /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m32bcst | xmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | xmm {k}{z}, xmm, m128/m32bcst | ymm {k}{z}, ymm, m256/m32bcst |
|---|---|---|---|---|---|
| Skylake-SP, Ice Lake | 1 / 0.5p05 | 8 / 0.5p05 | 1 / 0.33p015 | 7 / 0.5p015 | 8 / 0.5p015 |
| Sapphire Rapids | 1 / 0.5p05 | 9 / 0.5p05 | 1 / 0.33p015 | 8 / 0.33p015 | 9 / 0.33p015 |
| Zen 4 | 1 / 0.5FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 |
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.
Every doubleword works alike: 4, 8 and 16 doublewords in the xmm, ymm and zmm forms. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m32bcst, one doubleword from memory stands for every element of the last source.
Result doubleword i comes from doubleword i of xmm2 and xmm3. Result doublewords 3 to 0: a3^b3, unchanged (bit 2 of k1 is 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 // 32):
if k1[i]:
zmm1.d[i] = zmm2.d[i] ^ src3.d[i]
elif zeroing:
zmm1.d[i] = 0
# else: zmm1.d[i] keeps its value
# m32bcst: src3.d[i] is the m32 for every i
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPXORD xmm {k}{z}, xmm, xmm/m128/m32bcst VPXORD ymm {k}{z}, ymm, ymm/m256/m32bcst VPXORD zmm {k}{z}, zmm, zmm/m512/m32bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | explicit | read |
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 VPXORD, 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.
| Intrinsic | Compiles to |
|---|---|
_mm_mask_xor_epi32
__m128i _mm_mask_xor_epi32(__m128i __W, __mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_mask_xor_ps
__m128 _mm_mask_xor_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B) |
|
_mm_maskz_xor_epi32
__m128i _mm_maskz_xor_epi32(__mmask8 __U, __m128i __A, __m128i __B) |
|
_mm_maskz_xor_ps
__m128 _mm_maskz_xor_ps(__mmask8 __U, __m128 __A, __m128 __B) |
|
_mm256_mask_xor_epi32
__m256i _mm256_mask_xor_epi32(__m256i __W, __mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_mask_xor_ps
__m256 _mm256_mask_xor_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B) |
|
_mm256_maskz_xor_epi32
__m256i _mm256_maskz_xor_epi32(__mmask8 __U, __m256i __A, __m256i __B) |
|
_mm256_maskz_xor_ps
__m256 _mm256_maskz_xor_ps(__mmask8 __U, __m256 __A, __m256 __B) |
|
_mm512_xor_epi32
__m512i _mm512_xor_epi32(__m512i __a, __m512i __b) |
|
_mm512_xor_ps
__m512 _mm512_xor_ps(__m512 __A, __m512 __B) |
|
_mm512_mask_xor_epi32
__m512i _mm512_mask_xor_epi32(__m512i __src, __mmask16 __k, __m512i __a, __m512i __b) |
|
_mm512_mask_xor_ps
__m512 _mm512_mask_xor_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_maskz_xor_epi32
__m512i _mm512_maskz_xor_epi32(__mmask16 __k, __m512i __a, __m512i __b) |
|
_mm512_maskz_xor_ps
__m512 _mm512_maskz_xor_ps(__mmask16 __U, __m512 __A, __m512 __B) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512F_512 | AVX10.1 or 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 or AVX512F + 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_128 | Same as AVX512F_128 |
More AVX10.1 instructions
- VPSUBUSW
- VPSUBW
- VPTERNLOGD
- VPTERNLOGQ
- VPTESTMB
- VPTESTMD
- VPTESTMQ
- VPTESTMW
- VPTESTNMB
- VPTESTNMD
- VPTESTNMQ
- VPTESTNMW
- VPUNPCKHBW
- VPUNPCKHDQ
- VPUNPCKHQDQ
- VPUNPCKHWD
- VPUNPCKLBW
- VPUNPCKLDQ
- VPUNPCKLQDQ
- VPUNPCKLWD
- VPXORQ
- VRANGEPD
- VRANGEPS
- VRANGESD
- VRANGESS
- VRCP14PD
- VRCP14PS
- VRCP14SD
- VRCP14SS
- VRCPPH
- VRCPSH
- VREDUCEPD
- VREDUCEPH
- VREDUCEPS
- VREDUCESD
- VREDUCESH
- VREDUCESS
- VRNDSCALEPD
- VRNDSCALEPH
- VRNDSCALEPS
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-530 (PXOR)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
- 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.