Instruction
VPCMPUQ
Compares packed unsigned quadwords with a predicate chosen by an immediate and writes the results to a mask register.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VPCMPUQ compares 2, 4 or 8 pairs of quadwords as unsigned integers and writes one bit per pair to a mask register. VPCMPQ is its signed twin and shows what AVX2 code does instead, flipping the sign bits of both operands before a signed VPCMPGTQ; VPCMPD explains the predicates of the immediate and the write mask, which clears bits rather than merging them. Like the other compares of AVX-512F, it takes a broadcast quadword as its second source.
Where the sign bit counts
The signed and unsigned compares disagree whenever exactly one operand
has its top bit set. On Zen 5,
vpcmpuq k3{k5}, zmm0, zmm31, 0x5, greater or equal, set the bit of
the pair 8000000000000000h and 1, which a signed compare would order
the other way, and left clear the pairs that put 8000000000000000h and
7FFFFFFFFFFFFFFFh against FFFFFFFFFFFFFFFFh, the largest unsigned
quadword. With 1 against 1 also passing, the result was 21h: the bits
of elements 0 and 5, of the four that K5 selected.
Ranges in one compare
Unsigned order turns lo <= x && x <= hi into a single test,
x - lo <= hi - lo, since every x below lo wraps around to a large
number; VPCMPUB does the same with letters. For
d[i] = a[i] - lo <= hi - lo ? a[i] : 0 over 1024 uint64_t
elements, GCC 14 and Clang 23 at -O2 with -march=x86-64-v4 emit a
VPSUBQ and one VPCMPUQ with predicate 2, less or
equal (Clang prints it vpcmpleuq), and a zero-masked
VMOVDQA64. A bounds check works the same way:
(uint64_t)x[i] < (uint64_t)n rejects negative indices as well as
those past the end, in one VPCMPUQ with predicate 1. The compilers do
not make that rewrite for x[i] >= 0 && x[i] < n themselves, since n
could be negative: both emit two signed compares there, the second
under the first one’s mask.
AMD’s latency spreadsheet for Zen 5 lists VPCMPUQ as it lists VPCMPQ: one macro-op, two for a memory source, with a latency of 3, 4 and 6 cycles for XMM, YMM and ZMM.
In the optimization guide
What the optimization guide says about VPCMPUQ, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Zen 4
- Vectors and floating point: An AVX-512 compare that writes a mask register, such as VPCMPD, takes 3, 4 or 5 cycles for 128, 256 or 512 bits, where the older compares into a vector register take one cycle for integers and two for floats. sources differ
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VPCMPUQ k {k}, zmm, zmm, imm8
VPCMPUQ_MASKmskw_MASKmskw_ZMMu64_ZMMu64_IMM8_AVX512 | EVEX.512.66.0F3A.W1 1E /r ib | AVX10.1 or AVX512F |
VPCMPUQ k {k}, zmm, m512/m64bcst, imm8
VPCMPUQ_MASKmskw_MASKmskw_ZMMu64_MEMu64_IMM8_AVX512 | EVEX.512.66.0F3A.W1 1E /r ib | AVX10.1 or AVX512F |
VPCMPUQ k {k}, xmm, xmm, imm8
VPCMPUQ_MASKmskw_MASKmskw_XMMu64_XMMu64_IMM8_AVX512 | EVEX.128.66.0F3A.W1 1E /r ib | AVX10.1 or AVX512F + AVX512VL |
VPCMPUQ k {k}, xmm, m128/m64bcst, imm8
VPCMPUQ_MASKmskw_MASKmskw_XMMu64_MEMu64_IMM8_AVX512 | EVEX.128.66.0F3A.W1 1E /r ib | AVX10.1 or AVX512F + AVX512VL |
VPCMPUQ k {k}, ymm, ymm, imm8
VPCMPUQ_MASKmskw_MASKmskw_YMMu64_YMMu64_IMM8_AVX512 | EVEX.256.66.0F3A.W1 1E /r ib | AVX10.1 or AVX512F + AVX512VL |
VPCMPUQ k {k}, ymm, m256/m64bcst, imm8
VPCMPUQ_MASKmskw_MASKmskw_YMMu64_MEMu64_IMM8_AVX512 | EVEX.256.66.0F3A.W1 1E /r ib | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | k {k}, zmm, zmm, imm8 | k {k}, zmm, m512/m64bcst, imm8k {k}, ymm, m256/m64bcst, imm8 | k {k}, xmm, xmm, imm8k {k}, ymm, ymm, imm8 | k {k}, xmm, m128/m64bcst, imm8 |
|---|---|---|---|---|
| Skylake-SP, Ice Lake | 4 / 1p5 | 11 / 1p5 | 4 / 1p5 | 10 / 1p5 |
| Sapphire Rapids | 3 / 1p5 | 3 / 1p5 | 3 / 1p5 | 3 / 1p5 |
| Zen 4 | 1 / 0.5FP0 FP1 FP2 FP3 | 8 / 0.5FP0 FP1 FP2 FP3 | 1 / 0.251FP0 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.
Where a bit of the write mask k2 is 0, the result bit is 0. Every quadword works alike: 2, 4 and 8 quadwords in the xmm, ymm and zmm forms. With m64bcst, one quadword from memory stands for every element of the last source.
Bit i of k1 comes from quadword i of xmm2 and xmm3. Result bits 1 to 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 // 64):
a = zmm2.q[i]
b = src3.q[i]
k1[i] = k2[i] and compare(imm8, a, b)
# imm8 & 7: 0 ==, 1 <, 2 <=, 3 false, 4 !=, 5 >=, 6 >, 7 true
# m64bcst: src3.q[i] is the m64 for every i
# the other bits of k1 are clearedRun on AMD Zen 5 (EPYC 9645): 6 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VPCMPUQ k {k}, xmm, xmm/m128/m64bcst, imm8 VPCMPUQ k {k}, ymm, ymm/m256/m64bcst, imm8 VPCMPUQ k {k}, zmm, zmm/m512/m64bcst, imm8 | ||
k | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcst | explicit | read |
imm8 | 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 VPCMPUQ, 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_cmp_epu64_mask
__mmask8 _mm_cmp_epu64_mask(__m128i a, __m128i b, const int p) |
|
_mm_cmpge_epu64_mask
__mmask8 _mm_cmpge_epu64_mask(__m128i A, __m128i B) |
|
_mm_cmpgt_epu64_mask
__mmask8 _mm_cmpgt_epu64_mask(__m128i A, __m128i B) |
|
_mm_cmple_epu64_mask
__mmask8 _mm_cmple_epu64_mask(__m128i A, __m128i B) |
|
_mm_cmplt_epu64_mask
__mmask8 _mm_cmplt_epu64_mask(__m128i A, __m128i B) |
|
_mm_mask_cmp_epu64_mask
__mmask8 _mm_mask_cmp_epu64_mask(__mmask8 m, __m128i a, __m128i b, const int p) |
|
_mm_mask_cmpge_epu64_mask
__mmask8 _mm_mask_cmpge_epu64_mask(__mmask8 k, __m128i A, __m128i B) |
|
_mm_mask_cmpgt_epu64_mask
__mmask8 _mm_mask_cmpgt_epu64_mask(__mmask8 k, __m128i A, __m128i B) |
|
_mm_mask_cmple_epu64_mask
__mmask8 _mm_mask_cmple_epu64_mask(__mmask8 k, __m128i A, __m128i B) |
|
_mm_mask_cmplt_epu64_mask
__mmask8 _mm_mask_cmplt_epu64_mask(__mmask8 k, __m128i A, __m128i B) |
|
_mm256_cmp_epu64_mask
__mmask8 _mm256_cmp_epu64_mask(__m256i a, __m256i b, const int p) |
|
_mm256_cmpge_epu64_mask
__mmask8 _mm256_cmpge_epu64_mask(__m256i A, __m256i B) |
|
_mm256_cmpgt_epu64_mask
__mmask8 _mm256_cmpgt_epu64_mask(__m256i A, __m256i B) |
|
_mm256_cmple_epu64_mask
__mmask8 _mm256_cmple_epu64_mask(__m256i A, __m256i B) |
|
_mm256_cmplt_epu64_mask
__mmask8 _mm256_cmplt_epu64_mask(__m256i A, __m256i B) |
|
_mm256_mask_cmp_epu64_mask
__mmask8 _mm256_mask_cmp_epu64_mask(__mmask8 m, __m256i a, __m256i b, const int p) |
|
_mm256_mask_cmpge_epu64_mask
__mmask8 _mm256_mask_cmpge_epu64_mask(__mmask8 k, __m256i A, __m256i B) |
|
_mm256_mask_cmpgt_epu64_mask
__mmask8 _mm256_mask_cmpgt_epu64_mask(__mmask8 k, __m256i A, __m256i B) |
|
_mm256_mask_cmple_epu64_mask
__mmask8 _mm256_mask_cmple_epu64_mask(__mmask8 k, __m256i A, __m256i B) |
|
_mm256_mask_cmplt_epu64_mask
__mmask8 _mm256_mask_cmplt_epu64_mask(__mmask8 k, __m256i A, __m256i B) |
|
_mm512_cmp_epu64_mask
__mmask8 _mm512_cmp_epu64_mask(__m512i a, __m512i b, const int p) |
|
_mm512_mask_cmp_epu64_mask
__mmask8 _mm512_mask_cmp_epu64_mask(__mmask8 m, __m512i a, __m512i b, const int p) |
|
_mm512_cmpge_epu64_mask
__mmask8 _mm512_cmpge_epu64_mask(__m512i A, __m512i B) |
|
_mm512_mask_cmpge_epu64_mask
__mmask8 _mm512_mask_cmpge_epu64_mask(__mmask8 k, __m512i A, __m512i B) |
|
_mm512_cmpgt_epu64_mask
__mmask8 _mm512_cmpgt_epu64_mask(__m512i A, __m512i B) |
|
_mm512_mask_cmpgt_epu64_mask
__mmask8 _mm512_mask_cmpgt_epu64_mask(__mmask8 k, __m512i A, __m512i B) |
|
_mm512_cmple_epu64_mask
__mmask8 _mm512_cmple_epu64_mask(__m512i A, __m512i B) |
|
_mm512_mask_cmple_epu64_mask
__mmask8 _mm512_mask_cmple_epu64_mask(__mmask8 k, __m512i A, __m512i B) |
|
_mm512_cmplt_epu64_mask
__mmask8 _mm512_cmplt_epu64_mask(__m512i A, __m512i B) |
|
_mm512_mask_cmplt_epu64_mask
__mmask8 _mm512_mask_cmplt_epu64_mask(__mmask8 k, __m512i A, __m512i 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
- VPBROADCASTB
- VPBROADCASTD
- VPBROADCASTMB2Q
- VPBROADCASTMW2D
- VPBROADCASTQ
- VPBROADCASTW
- VPCLMULQDQ
- VPCMPB
- VPCMPD
- VPCMPEQB
- VPCMPEQD
- VPCMPEQQ
- VPCMPEQW
- VPCMPGTB
- VPCMPGTD
- VPCMPGTQ
- VPCMPGTW
- VPCMPQ
- VPCMPUB
- VPCMPUD
- VPCMPUW
- VPCMPW
- VPCOMPRESSB
- VPCOMPRESSD
- VPCOMPRESSQ
- VPCOMPRESSW
- VPCONFLICTD
- VPCONFLICTQ
- VPDPBUSD
- VPDPBUSDS
- VPDPWSSD
- VPDPWSSDS
- VPERMB
- VPERMD
- VPERMI2B
- VPERMI2D
- VPERMI2PD
- VPERMI2PS
- VPERMI2Q
- VPERMI2W
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 2C, page 5-462 (VPCMPQ/
VPCMPUQ) - 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.