Instruction
VMAXPD
Returns the larger of each pair of packed doubles, or the second operand if either is NaN or both are zero.
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, xmm9with 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
| Instruction | Encoding | Requires |
|---|---|---|
VMAXPD xmm, xmm, m128
VMAXPD_XMMdq_XMMdq_MEMdq | VEX.128.66.0F.WIG 5F /r | AVX |
VMAXPD xmm, xmm, xmm
VMAXPD_XMMdq_XMMdq_XMMdq | VEX.128.66.0F.WIG 5F /r | AVX |
VMAXPD ymm, ymm, m256
VMAXPD_YMMqq_YMMqq_MEMqq | VEX.256.66.0F.WIG 5F /r | AVX |
VMAXPD ymm, ymm, ymm
VMAXPD_YMMqq_YMMqq_YMMqq | VEX.256.66.0F.WIG 5F /r | AVX |
VMAXPD zmm {k}{z}, zmm, zmm, {sae}
VMAXPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_AVX512 | EVEX.512.66.0F.W1 5F /r | AVX10.1 or AVX512F |
VMAXPD zmm {k}{z}, zmm, m512/m64bcst
VMAXPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_AVX512 | EVEX.512.66.0F.W1 5F /r | AVX10.1 or AVX512F |
VMAXPD xmm {k}{z}, xmm, xmm
VMAXPD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512 | EVEX.128.66.0F.W1 5F /r | AVX10.1 or AVX512F + AVX512VL |
VMAXPD xmm {k}{z}, xmm, m128/m64bcst
VMAXPD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512 | EVEX.128.66.0F.W1 5F /r | AVX10.1 or AVX512F + AVX512VL |
VMAXPD ymm {k}{z}, ymm, ymm
VMAXPD_YMMf64_MASKmskw_YMMf64_YMMf64_AVX512 | EVEX.256.66.0F.W1 5F /r | AVX10.1 or AVX512F + AVX512VL |
VMAXPD ymm {k}{z}, ymm, m256/m64bcst
VMAXPD_YMMf64_MASKmskw_YMMf64_MEMf64_AVX512 | EVEX.256.66.0F.W1 5F /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m64bcst | xmm, xmm, xmm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m64bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm, {sae} | zmm {k}{z}, zmm, m512/m64bcst | xmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm |
|---|---|---|---|---|---|---|---|
| Sandy Bridge, Haswell | 9 / 1p1 | 3 / 1p1 | 10 / 1p1 | 3 / 1p1 | |||
| Broadwell | 8 / 1p1 | 3 / 1p1 | 9 / 1p1 | 3 / 1p1 | |||
| Skylake | 10 / 0.5p01 | 4 / 0.5p01 | 11 / 0.5p01 | 4 / 0.5p01 | |||
| Skylake-SP, Ice Lake | 10 / 0.5p01 | 4 / 0.5p01 | 11 / 0.5p01 | 4 / 0.5p01 | 4 / 0.5p05 | 11 / 0.5p05 | 4 / 0.5p01 |
| Alder Lake | 11 / 0.5p01 | 4 / 0.5p01 | 12 / 0.5p01 | 4 / 0.5p01 | |||
| Sapphire Rapids | 11 / 0.5p01 | 4 / 0.5p01 | 12 / 0.5p01 | 4 / 0.5p01 | 4 / 1p0 | 12 / 1p0 | 4 / 0.5p01 |
| Lunar Lake | 10 / 2V0 V1 | 4 / 2V0 V1 | 11 / 2.33V0 V1 | 4 / 2V0 V1 | |||
| Piledriver | 7 / 1.5FPFMA FPU0 | 2 / 1FPFMA FPU0 | 7 / 1.5FPFMA FPU0 | 2 / 1FPFMA FPU0 | |||
| Zen | 8 / 0.5FPU0 FPU1 | 1 / 0.5FPU0 FPU1 | 8 / 1FPU0 FPU1 | 1 / 1FPU0 FPU1 | |||
| Zen 2 | 8 / 0.5FPU0 FPU1 | 1 / 0.5FPU0 FPU1 | 8 / 0.5FPU0 FPU1 | 1 / 0.5FPU0 FPU1 | |||
| Zen 3 | 8 / 0.5FP0 FP1 | 1 / 0.5FP0 FP1 | 8 / 0.5FP0 FP1 | 1 / 0.5FP0 FP1 | |||
| Zen 4 | 9 / 0.5FP0 FP1 | 2 / 0.5FP0 FP1 | 9 / 0.5FP0 FP1 | 2 / 0.5FP0 FP1 | 2 / 1FP0 FP1 | 9 / 1FP0 FP1 | 2 / 11FP0 FP1 |
| Jaguar | 7 / 1FPA FPU0 | 2 / 1FPA FPU0 | 7 / 2FPA FPU0 | 2 / 2FPA FPU0 | |||
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 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 upRun on AMD Zen 5 (EPYC 9645): 15 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VMAXPD xmm, xmm, xmm/m128 VMAXPD ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
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, 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-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.
| Intrinsic | Compiles to |
|---|---|
_mm_max_pd
__m128d _mm_max_pd(__m128d __a, __m128d __b) |
|
_mm_mask_max_pd
__m128d _mm_mask_max_pd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B) |
|
_mm_maskz_max_pd
__m128d _mm_maskz_max_pd(__mmask8 __U, __m128d __A, __m128d __B) |
|
_mm256_max_pd
__m256d _mm256_max_pd(__m256d __a, __m256d __b) |
|
_mm256_mask_max_pd
__m256d _mm256_mask_max_pd(__m256d __W, __mmask8 __U, __m256d __A, __m256d __B) |
|
_mm256_maskz_max_pd
__m256d _mm256_maskz_max_pd(__mmask8 __U, __m256d __A, __m256d __B) |
|
_mm512_max_pd
__m512d _mm512_max_pd(__m512d __A, __m512d __B) |
|
_mm512_max_round_pd
__m512d _mm512_max_round_pd(__m512d A, __m512d B, const int R) |
|
_mm512_mask_max_pd
__m512d _mm512_mask_max_pd(__m512d __W, __mmask8 __U, __m512d __A, __m512d __B) |
|
_mm512_mask_max_round_pd
__m512d _mm512_mask_max_round_pd(__m512d W, __mmask8 U, __m512d A, __m512d B, const int R) |
|
_mm512_maskz_max_pd
__m512d _mm512_maskz_max_pd(__mmask8 __U, __m512d __A, __m512d __B) |
|
_mm512_maskz_max_round_pd
__m512d _mm512_maskz_max_round_pd(__mmask8 U, __m512d A, __m512d B, const int R) |
|
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
- VCVTTSS2SI
- VDIVPD
- VDIVPS
- VDIVSD
- VDIVSS
- VDPPD
- VDPPS
- VEXTRACTF128
- VEXTRACTPS
- VHADDPD
- VHADDPS
- VHSUBPD
- VHSUBPS
- VINSERTF128
- VINSERTPS
- VLDDQU
- VLDMXCSR
- VMASKMOVDQU
- VMASKMOVPD
- VMASKMOVPS
- VMAXPS
- VMAXSD
- VMAXSS
- VMINPD
- VMINPS
- VMINSD
- VMINSS
- VMOVAPD
- VMOVAPS
- VMOVD
- VMOVDDUP
- VMOVDQA
- VMOVDQU
- VMOVHLPS
- VMOVHPD
- VMOVHPS
- VMOVLHPS
- VMOVLPD
- VMOVLPS
- VMOVMSKPD
More AVX10.1 instructions
- VGETEXPSH
- VGETEXPSS
- VGETMANTPD
- VGETMANTPH
- VGETMANTPS
- VGETMANTSD
- VGETMANTSH
- VGETMANTSS
- VGF2P8AFFINEINVQB
- VGF2P8AFFINEQB
- VGF2P8MULB
- VINSERTF32X4
- VINSERTF32X8
- VINSERTF64X2
- VINSERTF64X4
- VINSERTI32X4
- VINSERTI32X8
- VINSERTI64X2
- VINSERTI64X4
- VINSERTPS
- VMAXPH
- VMAXPS
- VMAXSD
- VMAXSH
- VMAXSS
- VMINPD
- VMINPH
- VMINPS
- VMINSD
- VMINSH
- VMINSS
- VMOVAPD
- VMOVAPS
- VMOVD
- VMOVDDUP
- VMOVDQA32
- VMOVDQA64
- VMOVDQU16
- VMOVDQU32
- VMOVDQU64
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 2B, page 4-5 (MAXPD)
- 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)
- AMD64 Architecture Programmer's Manual, Volume 4: 128-Bit, 256-Bit, and 512-Bit Media Instructions (26568, rev. 3.27, July 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.