Instruction
VXORPD
Computes the bitwise XOR of packed doubles.
VXORPD is the bitwise exclusive OR of two vectors, read as 64-bit elements: VXORPS with another element size. The XORPS and VXORPS pages cover its uses, zeroing a register and flipping signs, and what a write mask does to an XOR of a register with itself. The bits of the result are the same in both forms; the element size counts only for the EVEX form’s write mask and its broadcast of one 64-bit value, and that form needs AVX512DQ (AVX512F alone has the integer VPXORQ).
The same code, two spellings
GCC 14 and Clang 23 at -O2 write the same operations on doubles with different instructions:
_mm256_setzero_pd()isvxorpd xmm0, xmm0, xmm0in GCC and VXORPS in Clang. Both zero only xmm0 in the source, since a VEX instruction clears the bits above its result: the case recorded on Zen 5 withvxorpd xmm0, xmm13, xmm9left bits 128 to 511 of zmm0 zero.-b[i]over an array of doubles, with-march=x86-64-v3, is VXORPD with a broadcast -0.0 in GCC and VXORPS with the same constant in Clang; with-march=x86-64-v4, GCC uses VXORPD on zmm registers.
Neither choice changes the result, and AMD’s Zen 5 guide lists both forms alike, with a latency of 1 cycle on all four vector pipes.
Bits, not numbers
Because the operation sees only bits, Zen 5’s recorded cases show what
an arithmetic instruction would not do. vxorpd ymm12, ymm6, ymmword ptr [mem] turned two denormals, 15 and 1 times 2^-1074 as bit patterns,
into 14 times 2^-1074, and 16 and 1 into 17, with MXCSR untouched; a
NaN whose bits were all ones, XORed with the smallest denormal, became
another NaN with the last bit clear. A sign flip by XOR with -0.0 is
therefore exact for every input, NaNs included, which is why compilers
use it for negation instead of a subtraction from zero (see
VSUBPS).
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VXORPD xmm, xmm, m128
VXORPD_XMMdq_XMMdq_MEMdq | VEX.128.66.0F.WIG 57 /r | AVX |
VXORPD xmm, xmm, xmm
VXORPD_XMMdq_XMMdq_XMMdq | VEX.128.66.0F.WIG 57 /r | AVX |
VXORPD ymm, ymm, m256
VXORPD_YMMqq_YMMqq_MEMqq | VEX.256.66.0F.WIG 57 /r | AVX |
VXORPD ymm, ymm, ymm
VXORPD_YMMqq_YMMqq_YMMqq | VEX.256.66.0F.WIG 57 /r | AVX |
VXORPD xmm {k}{z}, xmm, xmm
VXORPD_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512 | EVEX.128.66.0F.W1 57 /r | AVX10.1 or AVX512DQ + AVX512VL |
VXORPD xmm {k}{z}, xmm, m128/m64bcst
VXORPD_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512 | EVEX.128.66.0F.W1 57 /r | AVX10.1 or AVX512DQ + AVX512VL |
VXORPD ymm {k}{z}, ymm, ymm
VXORPD_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512 | EVEX.256.66.0F.W1 57 /r | AVX10.1 or AVX512DQ + AVX512VL |
VXORPD ymm {k}{z}, ymm, m256/m64bcst
VXORPD_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512 | EVEX.256.66.0F.W1 57 /r | AVX10.1 or AVX512DQ + AVX512VL |
VXORPD zmm {k}{z}, zmm, zmm
VXORPD_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512 | EVEX.512.66.0F.W1 57 /r | AVX10.1 or AVX512DQ |
VXORPD zmm {k}{z}, zmm, m512/m64bcst
VXORPD_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512 | EVEX.512.66.0F.W1 57 /r | AVX10.1 or AVX512DQ |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m64bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m64bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm | zmm {k}{z}, zmm, m512/m64bcst |
|---|---|---|---|---|---|---|
| Sandy Bridge, Haswell | 7 / 1p5 | 1 / 1p5 | 8 / 1p5 | 1 / 1p5 | ||
| Broadwell | 6 / 1p5 | 1 / 1p5 | 7 / 1p5 | 1 / 1p5 | ||
| Skylake | 7 / 0.5p015 | 1 / 0.33p015 | 8 / 0.5p015 | 1 / 0.33p015 | ||
| Skylake-SP, Ice Lake | 7 / 0.5p015 | 1 / 0.33p015 | 8 / 0.5p015 | 1 / 0.33p015 | 1 / 0.5p05 | 8 / 0.5p05 |
| Alder Lake | 8 / 0.33p015 | 1 / 0.33p015 | 9 / 0.33p015 | 1 / 0.33p015 | ||
| Sapphire Rapids | 8 / 0.33p015 | 1 / 0.33p015 | 9 / 0.33p015 | 1 / 0.33p015 | 1 / 0.5p05 | 9 / 0.5p05 |
| Lunar Lake | 7 / 2V0 V1 V2 V3 | 1 / 0.25V0 V1 V2 V3 | 8 / 2.33V0 V1 V2 V3 | 1 / 0.25V0 V1 V2 V3 | ||
| Piledriver | 7 / 1.5FPMAL | 2 / 0.5FPMAL FPU2 FPU3 | 7 / 1.5FPMAL | 2 / 1FPMAL FPU2 FPU3 | ||
| Zen | 8 / 0.5FPU0 FPU1 FPU2 FPU3 | 1 / 0.25FPU0 FPU1 FPU2 FPU3 | 8 / 0.5FPU0 FPU1 FPU2 FPU3 | 1 / 0.5FPU0 FPU1 FPU2 FPU3 | ||
| Zen 2 | 8 / 0.33FPU0 FPU1 FPU2 FPU3 | 1 / 0.25FPU0 FPU1 FPU2 FPU3 | 8 / 0.33FPU0 FPU1 FPU2 FPU3 | 1 / 0.25FPU0 FPU1 FPU2 FPU3 | ||
| Zen 3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | ||
| Zen 4 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.25FP0 FP1 FP2 FP3 | 1 / 0.5FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 |
| Jaguar | 6 / 1FPA FPM FPU0 FPU1 | 1 / 0.5FPA FPM FPU0 FPU1 | 6 / 2FPA FPM FPU0 FPU1 | 1 / 1FPA FPM FPU0 FPU1 | ||
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 quadword works alike: 2, 4 and 8 quadwords in the xmm, ymm and zmm forms. The EVEX forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m64bcst, one quadword from memory stands for every element of the last source.
Result quadword i comes from quadword i of xmm2 and xmm3. Result quadwords 1 to 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 // 64):
if k1[i]: # 1 without a write mask
zmm1.q[i] = zmm2.q[i] ^ src3.q[i]
elif zeroing:
zmm1.q[i] = 0
# else: zmm1.q[i] keeps its value
# m64bcst: src3.q[i] is the m64 for every i
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 10 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VXORPD xmm, xmm, xmm/m128 VXORPD ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VXORPD xmm {k}{z}, xmm, xmm/m128/m64bcst VXORPD ymm {k}{z}, ymm, ymm/m256/m64bcst VXORPD zmm {k}{z}, zmm, zmm/m512/m64bcst | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | 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.
- VEX forms
avx-type-4- EVEX forms
AVX512-E4
Attributes
What else XED records about the forms. How to read.
- EVEX forms
- write masking
- EVEX memory forms
- embedded broadcast (tuple Full); memory fault suppression
Intrinsics
The C intrinsics of Clang 23.1.2 that compile to VXORPD, 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 |
|---|---|
_mm256_xor_pd
__m256d _mm256_xor_pd(__m256d __a, __m256d __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.
More AVX instructions
- VPTEST
- VPUNPCKHBW
- VPUNPCKHDQ
- VPUNPCKHQDQ
- VPUNPCKHWD
- VPUNPCKLBW
- VPUNPCKLDQ
- VPUNPCKLQDQ
- VPUNPCKLWD
- VPXOR
- VRCPPS
- VRCPSS
- VROUNDPD
- VROUNDPS
- VROUNDSD
- VROUNDSS
- VRSQRTPS
- VRSQRTSS
- VSHUFPD
- VSHUFPS
- VSQRTPD
- VSQRTPS
- VSQRTSD
- VSQRTSS
- VSTMXCSR
- VSUBPD
- VSUBPS
- VSUBSD
- VSUBSS
- VTESTPD
- VTESTPS
- VUCOMISD
- VUCOMISS
- VUNPCKHPD
- VUNPCKHPS
- VUNPCKLPD
- VUNPCKLPS
- VXORPS
- VZEROALL
- VZEROUPPER
More AVX10.1 instructions
- VRSQRT14SD
- VRSQRT14SS
- VRSQRTPH
- VRSQRTSH
- VSCALEFPD
- VSCALEFPH
- VSCALEFPS
- VSCALEFSD
- VSCALEFSH
- VSCALEFSS
- VSCATTERDPD
- VSCATTERDPS
- VSCATTERQPD
- VSCATTERQPS
- VSHUFF32X4
- VSHUFF64X2
- VSHUFI32X4
- VSHUFI64X2
- VSHUFPD
- VSHUFPS
- VSQRTPD
- VSQRTPH
- VSQRTPS
- VSQRTSD
- VSQRTSH
- VSQRTSS
- VSUBPD
- VSUBPH
- VSUBPS
- VSUBSD
- VSUBSH
- VSUBSS
- VUCOMISD
- VUCOMISH
- VUCOMISS
- VUNPCKHPD
- VUNPCKHPS
- VUNPCKLPD
- VUNPCKLPS
- VXORPS
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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2D, page 6-42 (XORPD)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
- Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 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.