Extensions
Forms
10 (4 VEX, 6 EVEX)
Data
Intel XED v2026.08.23

VMAXPD keeps the larger double of each pair by the rule of VMAXPS, whose page covers the encodings and {sae}: the first source comes back only when it is greater than the second, so a NaN in either element, or two zeros of any sign, give the second source as it is. VMINPD is the mirror image. AMD’s Zen 5 guide lists it like VMAXPS, on the pipes FP2 and FP3 with a latency of 2 cycles.

Quiet NaNs are invalid too

An addition passes a quiet NaN on without a flag; a maximum does not. Intel’s manual counts a quiet NaN source among the invalid operations of MAXPD, while AMD’s table of its exceptions names only a signaling NaN. Zen 5’s recorded cases follow Intel’s:

  • vmaxpd xmm0, xmm13, xmm9 with two quiet NaNs, 7FF8000000000000h first and FFF8000000000000h second, returned the second and set IE.
  • With a quiet NaN first and a signaling NaN second, the signaling NaN came back unchanged, not quieted; in the other order the quiet one came back, and IE was set.

So code that runs with IE unmasked, or reads IE afterwards, sees a maximum of quiet NaNs as an invalid operation.

In compiled code

For b[i] > c[i] ? b[i] : c[i] over doubles, GCC 14 and Clang 23 at -O2 with -march=x86-64-v3 emit one VMAXPD per four elements with b as the first source, which gives c where b is a NaN, just as the C expression does. A ReLU, b[i] > 0.0 ? b[i] : 0.0, is VMAXPD against a register cleared by VXORPD, the zero second, so a NaN input comes out as 0. C’s fmax must return the number when only one argument is a NaN: GCC calls the library function for every element, and Clang follows each VMAXPD with VCMPPD (unordered) and VBLENDVPD, as it does for singles.

Forms

Every encoding of VMAXPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMAXPD xmm, xmm, m128 VMAXPD_XMMdq_XMMdq_MEMdqVEX.128.66.0F.WIG 5F /rAVX
VMAXPD xmm, xmm, xmm VMAXPD_XMMdq_XMMdq_XMMdqVEX.128.66.0F.WIG 5F /rAVX
VMAXPD ymm, ymm, m256 VMAXPD_YMMqq_YMMqq_MEMqqVEX.256.66.0F.WIG 5F /rAVX
VMAXPD ymm, ymm, ymm VMAXPD_YMMqq_YMMqq_YMMqqVEX.256.66.0F.WIG 5F /rAVX
VMAXPD zmm {k}{z}, zmm, zmm, {sae} VMAXPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512EVEX.512.66.0F.W1 5F /rAVX10.1 or AVX512F
VMAXPD zmm {k}{z}, zmm, m512/m64bcst VMAXPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512EVEX.512.66.0F.W1 5F /rAVX10.1 or AVX512F
VMAXPD xmm {k}{z}, xmm, xmm VMAXPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.128.66.0F.W1 5F /rAVX10.1 or AVX512F + AVX512VL
VMAXPD xmm {k}{z}, xmm, m128/m64bcst VMAXPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.128.66.0F.W1 5F /rAVX10.1 or AVX512F + AVX512VL
VMAXPD ymm {k}{z}, ymm, ymm VMAXPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512EVEX.256.66.0F.W1 5F /rAVX10.1 or AVX512F + AVX512VL
VMAXPD ymm {k}{z}, ymm, m256/m64bcst VMAXPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512EVEX.256.66.0F.W1 5F /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.
Modelxmm, xmm, m128
xmm {k}{z}, xmm, m128/m64bcst
xmm, xmm, xmmymm, ymm, m256
ymm {k}{z}, ymm, m256/m64bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmm, {sae}zmm {k}{z}, zmm, m512/m64bcstxmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
Sandy Bridge, Haswell9 / 1p13 / 1p110 / 1p13 / 1p1
Broadwell8 / 1p13 / 1p19 / 1p13 / 1p1
Skylake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p01
Skylake-SP, Ice Lake10 / 0.5p014 / 0.5p0111 / 0.5p014 / 0.5p014 / 0.5p0511 / 0.5p054 / 0.5p01
Alder Lake11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p01
Sapphire Rapids11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p014 / 1p012 / 1p04 / 0.5p01
Lunar Lake10 / 2V0 V14 / 2V0 V111 / 2.33V0 V14 / 2V0 V1
Piledriver7 / 1.5FPFMA FPU02 / 1FPFMA FPU07 / 1.5FPFMA FPU02 / 1FPFMA FPU0
Zen8 / 0.5FPU0 FPU11 / 0.5FPU0 FPU18 / 1FPU0 FPU11 / 1FPU0 FPU1
Zen 28 / 0.5FPU0 FPU11 / 0.5FPU0 FPU18 / 0.5FPU0 FPU11 / 0.5FPU0 FPU1
Zen 38 / 0.5FP0 FP11 / 0.5FP0 FP18 / 0.5FP0 FP11 / 0.5FP0 FP1
Zen 49 / 0.5FP0 FP12 / 0.5FP0 FP19 / 0.5FP0 FP12 / 0.5FP0 FP12 / 1FP0 FP19 / 1FP0 FP12 / 11FP0 FP1
Jaguar7 / 1FPA FPU02 / 1FPA FPU07 / 2FPA FPU02 / 2FPA FPU0
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 1549; AMD 58455, row 127).

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 double of the result comes from the double in the same place in each source.
VMAXPD: element by elementResult double i comes from double i of xmm2 and xmm3. Result doubles 1 to 0: r1, r0.01xmm2a11k1r0r1xmm101xmm3or m128b

Every double works alike: 2, 4 and 8 doubles 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 double from memory stands for every element of the last source.

Result double i comes from double i of xmm2 and xmm3. Result doubles 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]:  # 1 without a write mask
        a = zmm2.f64[i]
        b = src3.f64[i]
        zmm1.f64[i] = fmax(a, b)
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[i] keeps its value
# a NaN or two zeros: b
# m64bcst: src3.f64[i] is the m64 for every i
# {sae}: no exception flags
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 15 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
VMAXPD xmm, xmm, xmm/m128 VMAXPD ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
VMAXPD xmm {k}{z}, xmm, xmm/m128/m64bcst VMAXPD ymm {k}{z}, ymm, ymm/m256/m64bcst VMAXPD zmm {k}{z}, zmm, zmm/m512/m64bcst, {sae}
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.

VEX forms
avx-type-2
EVEX forms
AVX512-E2

Attributes

What else XED records about the forms. How to read.

All forms
follows MXCSR
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 VMAXPD, 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_pd __m128d _mm_max_pd(__m128d __a, __m128d __b)

VMAXPD xmm, xmm, xmm VEX.128 -mavxwith AVX enabled

_mm_mask_max_pd __m128d _mm_mask_max_pd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B)

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

_mm_maskz_max_pd __m128d _mm_maskz_max_pd(__mmask8 __U, __m128d __A, __m128d __B)

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

_mm256_max_pd __m256d _mm256_max_pd(__m256d __a, __m256d __b)

VMAXPD ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_max_pd __m256d _mm256_mask_max_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256d __B)

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

_mm256_maskz_max_pd __m256d _mm256_maskz_max_pd(__mmask8 __U, __m256d __A, __m256d __B)

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

_mm512_max_pd __m512d _mm512_max_pd(__m512d __A, __m512d __B)

VMAXPD zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_max_round_pd __m512d _mm512_max_round_pd(__m512d A, __m512d B, const int R)

VMAXPD zmm, zmm, zmm, {sae} EVEX.512 -mavx512f

_mm512_mask_max_pd __m512d _mm512_mask_max_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512d __B)

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

_mm512_mask_max_round_pd __m512d _mm512_mask_max_round_pd(__m512d W, __mmask8 U, __m512d A, __m512d B, const int R)

VMAXPD zmm {k}, zmm, zmm, {sae} EVEX.512 -mavx512f

_mm512_maskz_max_pd __m512d _mm512_maskz_max_pd(__mmask8 __U, __m512d __A, __m512d __B)

VMAXPD zmm {k}{z}, zmm, zmm EVEX.512 -mavx512f

_mm512_maskz_max_round_pd __m512d _mm512_maskz_max_round_pd(__mmask8 U, __m512d A, __m512d B, const int R)

VMAXPD zmm {k}{z}, zmm, zmm, {sae} 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
AVX

AVX
CPUID.01H:ECX[28] AVX

Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Comet Lake, Cannon Lake, Ice Lake (client), Tiger Lake, Alder Lake, Arrow Lake, Panther Lake, Nova Lake, Skylake-SP, Cascade Lake, Cooper Lake, Ice Lake (server), Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6
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 AVX instructions

All 253 AVX instructions

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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-5 (MAXPD)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  7. Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  8. AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit, 256-Bit, and 512-Bit Media Instructions (26568, rev. 3.27, July 2026)
  9. 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.