Extensions
Forms
2 (2 Legacy)
Data
Intel XED v2026.08.23

MAXPD keeps the larger double of each of two pairs, by the rule that VMAXPD and MAXPS set out: the first operand comes back only when it is greater than the second, so a NaN in either, or two zeros of any sign, give the second operand as it is. VMAXPD’s page also shows that a quiet NaN alone raises IE, as Intel’s manual says and AMD’s leaves out. MINPD is the mirror image.

The legacy encoding writes its result over the first operand and leaves bits 128 and up of the register as they were (see SSE and AVX for what mixing that with VEX code costs), and its memory operand must be aligned to 16 bytes. Zen 5’s two recorded cases, with the same doubles in a register and in memory, show the rule on NaNs:

  • a signaling NaN first and a quiet NaN second gave the quiet NaN, unchanged;
  • a quiet NaN first and 1.0 second gave 1.0, the NaN lost;
  • IE was set in both, and bits 511:128 of the destination stayed as they were.

In baseline code

MAXPD is SSE2, so x86-64 code uses it without options. In our builds at -O2, with the default target and with -march=x86-64-v2:

  • a[i] = b[i] > c[i] ? b[i] : c[i] over pointers is MAXPD in Clang 23, two per iteration, each after MOVUPD loads, and one MAXSD per element in GCC 14; over global arrays of fixed size both compilers emit MAXPD with the second operand read from memory.
  • A ReLU, b[i] > 0.0 ? b[i] : 0.0, is MAXPD against a register zeroed by XORPD in Clang, so a NaN comes out as 0.
  • C’s fmax must return the number when only one argument is a NaN. GCC calls the library function per element. Clang takes MAXPD with the operands swapped, which handles a NaN in the second argument, then finds NaNs in the first with CMPUNORDPD and picks the second argument there: with ANDPD, ANDNPD and ORPD for the default target, and with one BLENDVPD for x86-64-v2, which has SSE4.1.

Forms

Every encoding of MAXPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
MAXPD xmm, m128 MAXPD_XMMpd_MEMpd66 0F 5F /rSSE2
MAXPD xmm, xmm MAXPD_XMMpd_XMMpd66 0F 5F /rSSE2

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.
MAXPD: element by elementResult double i comes from double i of xmm1 and xmm2. Result doubles 1 to 0: r1, r0.01xmm1ar0r1xmm101xmm2or m128b

Result double i comes from double i of xmm1 and xmm2. 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(2):
    a = xmm1.f64[i]
    b = src2.f64[i]
    xmm1.f64[i] = fmax(a, b)
# a NaN or two zeros: b
# bits 128 and up of the register are unchanged

Run on AMD Zen 5 (EPYC 9645): 2 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
MAXPD xmm, xmm/m128
xmmexplicitread, write
xmm/m128explicitread

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
SSE_TYPE_2

Attributes

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

All forms
follows MXCSR
Memory forms
aligned memory operand

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to MAXPD, 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)

MAXPD xmm, xmm Legacy -msse2

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
SSE2

SSE2
CPUID.01H:EDX[26] SSE2

Every x86-64 processor in XED’s model and Zen 3 to Zen 6

More SSE2 instructions

All 124 SSE2 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. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-5 (MAXPD)
  5. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 1 (253665-093, September 2026)
  6. AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit and 256-Bit Media Instructions (26568, rev. 3.25, November 2021), Wayback Machine copy of AMD's PDF

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, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.