Extensions
Forms
6 (6 EVEX)
Data
Intel XED v2026.08.23

VPMAXUQ keeps the larger of each pair of quadwords, compared as unsigned integers: 2, 4 or 8 at a time, in EVEX encodings only, from AVX512F on. It is the partner of VPMINUQ, whose page shows what AVX2 code does instead, a sign flip, a signed compare and a blend, and the absolute difference that Clang builds from both. VPMAXUD is the doubleword form and VPMAXSQ the signed one.

Recorded on Zen 5

  • The top bit. vpmaxuq zmm9{k7}, zmm9, zmm14 chose FFFFFFFFFFFFFFFFh over 1 and over 7FFFFFFFFFFFFFFFh, and against a broadcast 1, vpmaxuq xmm1{k7}{z}, xmm2, [mem] kept 8000000000000000h twice, where a signed maximum gives 1.
  • A broadcast. Against a broadcast FFFFFFFFFFFFFFFFh, every element selected by K3 became all ones; the two left out kept their old bits.
  • Zeroing. vpmaxuq ymm24{k3}{z}, ymm3, ymm3 returned the elements that K3 selects, 7FFFFFFFFFFFFFFFh, 8000000000000000h and 1, and 0 for the one it leaves out.

In compiled code

At -O2 with -march=x86-64-v4, GCC 14 and Clang 23 compile `a[i] > b[i]
? a[i] : b[i]overuint64_tand a clamp from below,a[i] < 100 ? 100
a[i], to VPMAXUQ with memory as the second source. For the largest element of an array, GCC keeps one ZMM maximum in the loop and halves it at the end with [VEXTRACTI64X4](/insn/vextracti64x4/) and [VEXTRACTI64X2](/insn/vextracti64x2/); Clang keeps four YMM maximums. A saturating subtraction, a[i] > b[i] ? a[i] - b[i] : 0, is max(a, b) - bin Clang, VPMAXUQ and [VPSUBQ](/insn/vpsubq/), while GCC compares with [VPCMPUQ](/insn/vpcmpuq/) and subtracts under a zero mask._mm512_max_epu64` is one VPMAXUQ.

AMD’s Zen 5 latency spreadsheet gives one macro-op on pipe FP0 or FP3 and 2 cycles, as for VPMINUQ.

Forms

Every encoding of VPMAXUQ that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VPMAXUQ zmm {k}{z}, zmm, zmm VPMAXUQ_ZMMu64_MASKmskw_ZMMu64_ZMMu64_AVX512EVEX.512.66.0F38.W1 3F /rAVX10.1 or AVX512F
VPMAXUQ zmm {k}{z}, zmm, m512/m64bcst VPMAXUQ_ZMMu64_MASKmskw_ZMMu64_MEMu64_AVX512EVEX.512.66.0F38.W1 3F /rAVX10.1 or AVX512F
VPMAXUQ xmm {k}{z}, xmm, xmm VPMAXUQ_XMMu64_MASKmskw_XMMu64_XMMu64_AVX512EVEX.128.66.0F38.W1 3F /rAVX10.1 or AVX512F + AVX512VL
VPMAXUQ xmm {k}{z}, xmm, m128/m64bcst VPMAXUQ_XMMu64_MASKmskw_XMMu64_MEMu64_AVX512EVEX.128.66.0F38.W1 3F /rAVX10.1 or AVX512F + AVX512VL
VPMAXUQ ymm {k}{z}, ymm, ymm VPMAXUQ_YMMu64_MASKmskw_YMMu64_YMMu64_AVX512EVEX.256.66.0F38.W1 3F /rAVX10.1 or AVX512F + AVX512VL
VPMAXUQ ymm {k}{z}, ymm, m256/m64bcst VPMAXUQ_YMMu64_MASKmskw_YMMu64_MEMu64_AVX512EVEX.256.66.0F38.W1 3F /rAVX10.1 or AVX512F + AVX512VL

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.
Modelzmm {k}{z}, zmm, zmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
zmm {k}{z}, zmm, m512/m64bcst
ymm {k}{z}, ymm, m256/m64bcst
xmm {k}{z}, xmm, m128/m64bcst
Skylake-SP, Ice Lake3 / 1p510 / 1p59 / 1p5
Sapphire Rapids3 / 1p511 / 1p510 / 1p5
Zen 42 / 1FP0 FP18 / 0.5FP0 FP1 FP2 FP38 / 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.

Element-wise: each quadword of the result comes from the quadword in the same place in each source.
VPMAXUQ: element by elementResult quadword i comes from quadword i of xmm2 and xmm3. Result quadwords 1 to 0: r1, r0.01xmm2a11k1r0r1xmm101xmm3or m128b

Every quadword works alike: 2, 4 and 8 quadwords 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 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: 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):
    if k1[i]:
        a = zmm2.q[i]
        b = src3.q[i]
        zmm1.q[i] = max(a, b)
    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 up

Run on AMD Zen 5 (EPYC 9645): 6 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
VPMAXUQ xmm {k}{z}, xmm, xmm/m128/m64bcst VPMAXUQ ymm {k}{z}, ymm, ymm/m256/m64bcst VPMAXUQ zmm {k}{z}, zmm, zmm/m512/m64bcst
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread

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 VPMAXUQ, 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
_mm_max_epu64 __m128i _mm_max_epu64(__m128i __A, __m128i __B)

VPMAXUQ xmm, xmm, xmm EVEX.128 -mavx512vl

_mm_mask_max_epu64 __m128i _mm_mask_max_epu64(__m128i __W, __mmask8 __M, __m128i __A, __m128i __B)

VPMAXUQ xmm {k}, xmm, xmm EVEX.128 -mavx512vl

_mm_maskz_max_epu64 __m128i _mm_maskz_max_epu64(__mmask8 __M, __m128i __A, __m128i __B)

VPMAXUQ xmm {k}{z}, xmm, xmm EVEX.128 -mavx512vl

_mm256_max_epu64 __m256i _mm256_max_epu64(__m256i __A, __m256i __B)

VPMAXUQ ymm, ymm, ymm EVEX.256 -mavx512vl

_mm256_mask_max_epu64 __m256i _mm256_mask_max_epu64(__m256i __W, __mmask8 __M, __m256i __A, __m256i __B)

VPMAXUQ ymm {k}, ymm, ymm EVEX.256 -mavx512vl

_mm256_maskz_max_epu64 __m256i _mm256_maskz_max_epu64(__mmask8 __M, __m256i __A, __m256i __B)

VPMAXUQ ymm {k}{z}, ymm, ymm EVEX.256 -mavx512vl

_mm512_max_epu64 __m512i _mm512_max_epu64(__m512i __A, __m512i __B)

VPMAXUQ zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_mask_max_epu64 __m512i _mm512_mask_max_epu64(__m512i __W, __mmask8 __M, __m512i __A, __m512i __B)

VPMAXUQ zmm {k}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_max_epu64 __m512i _mm512_maskz_max_epu64(__mmask8 __M, __m512i __A, __m512i __B)

VPMAXUQ zmm {k}{z}, zmm, zmm EVEX.512 -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_512

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
AVX512F_128

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

or

AVX512F + AVX512VL
CPUID.(EAX=07H,ECX=0):EBX[16] AVX512F
CPUID.(EAX=07H,ECX=0):EBX[31] 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_128Same as AVX512F_128

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 2B, page 4-328 (PMAXUD/PMAXUQ)
  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.