Instruction
VMAXPS
Returns the larger of each pair of packed singles, or the second operand if either is NaN or both are zero.
VMAXPS keeps the larger single of each pair, by the same rule as the legacy MAXPS: it returns the first source only when that is greater than the second, and the second source otherwise. So when either element is a NaN, or both are zeros, the result is the second source as it is. Intel’s and AMD’s manuals agree on this; MINPS is the mirror image, and its page explains the rule at more length. Zen 5’s recorded cases show it:
- the maximum of +0 and -0 was -0, and that of -0 and +0 was +0;
- with a quiet NaN first and a signaling NaN second, the signaling NaN came back unchanged, still signaling, and IE was set;
- with a signaling NaN first and 1 second, the result was 1, and IE was set: unlike an addition, VMAXPS can drop a NaN;
- with DAZ set, a denormal second source came back as a zero of its sign.
In compiled code
The rule is that of b > c ? b : c, which GCC 14 and Clang 23 at -O2
compile to VMAXPS for -march=x86-64-v3 (ymm) and x86-64-v4 (zmm in
GCC, ymm in Clang). C’s fmaxf must return the number when only one
argument is a NaN: GCC calls the library, while Clang adds a check of
one argument with VCMPUNORDPS and takes the other where it is a NaN,
with VBLENDVPS for x86-64-v3 and a masked VMOVAPS for x86-64-v4.
Under -ffast-math both emit VMAXPS alone.
Encodings
The VEX forms add a separate destination and 256 bits, the EVEX forms
masking, a broadcast single and, between 512-bit registers, {sae}:
with every exception unmasked, Zen 5 compared a signaling NaN with 1
under {sae}, returned 1 and took no #XM. Code that needs
the maximum of IEEE 754-2019, in which +0 is greater than -0 and a NaN
input gives a NaN, can use AVX10.2’s VMINMAXPS.
AMD’s Zen 5 guide lists VMAXPS with a latency of 2 cycles at every
width.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VMAXPS xmm, xmm, m128
VMAXPS_XMMdq_XMMdq_MEMdq | VEX.128.NP.0F.WIG 5F /r | AVX |
VMAXPS xmm, xmm, xmm
VMAXPS_XMMdq_XMMdq_XMMdq | VEX.128.NP.0F.WIG 5F /r | AVX |
VMAXPS ymm, ymm, m256
VMAXPS_YMMqq_YMMqq_MEMqq | VEX.256.NP.0F.WIG 5F /r | AVX |
VMAXPS ymm, ymm, ymm
VMAXPS_YMMqq_YMMqq_YMMqq | VEX.256.NP.0F.WIG 5F /r | AVX |
VMAXPS zmm {k}{z}, zmm, zmm, {sae}
VMAXPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512 | EVEX.512.NP.0F.W0 5F /r | AVX10.1 or AVX512F |
VMAXPS zmm {k}{z}, zmm, m512/m32bcst
VMAXPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512 | EVEX.512.NP.0F.W0 5F /r | AVX10.1 or AVX512F |
VMAXPS xmm {k}{z}, xmm, xmm
VMAXPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512 | EVEX.128.NP.0F.W0 5F /r | AVX10.1 or AVX512F + AVX512VL |
VMAXPS xmm {k}{z}, xmm, m128/m32bcst
VMAXPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512 | EVEX.128.NP.0F.W0 5F /r | AVX10.1 or AVX512F + AVX512VL |
VMAXPS ymm {k}{z}, ymm, ymm
VMAXPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512 | EVEX.256.NP.0F.W0 5F /r | AVX10.1 or AVX512F + AVX512VL |
VMAXPS ymm {k}{z}, ymm, m256/m32bcst
VMAXPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512 | EVEX.256.NP.0F.W0 5F /r | AVX10.1 or AVX512F + AVX512VL |
Latency and throughput
| Model | xmm, xmm, m128xmm {k}{z}, xmm, m128/m32bcst | xmm, xmm, xmmxmm {k}{z}, xmm, xmmymm {k}{z}, ymm, ymm | ymm, ymm, m256ymm {k}{z}, ymm, m256/m32bcst | ymm, ymm, ymm | zmm {k}{z}, zmm, zmm, {sae} | zmm {k}{z}, zmm, m512/m32bcst |
|---|---|---|---|---|---|---|
| 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 |
| 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 |
| 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 |
| 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 single works alike: 4, 8 and 16 singles 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 m32bcst, one single from memory stands for every element of the last source.
Result single i comes from single i of xmm2 and xmm3. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 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 // 32):
if k1[i]: # 1 without a write mask
a = zmm2.f32[i]
b = src3.f32[i]
zmm1.f32[i] = fmax(a, b)
elif zeroing:
zmm1.f32[i] = 0
# else: zmm1.f32[i] keeps its value
# a NaN or two zeros: b
# m32bcst: src3.f32[i] is the m32 for every i
# {sae}: no exception flags
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 45 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VMAXPS xmm, xmm, xmm/m128 VMAXPS ymm, ymm, ymm/m256 | ||
xmm, ymm | explicit | write |
xmm, ymm | explicit | read |
xmm/m128, ymm/m256 | explicit | read |
VMAXPS xmm {k}{z}, xmm, xmm/m128/m32bcst VMAXPS ymm {k}{z}, ymm, ymm/m256/m32bcst VMAXPS zmm {k}{z}, zmm, zmm/m512/m32bcst, {sae} | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | 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 VMAXPS, 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_ps
__m128 _mm_max_ps(__m128 __a, __m128 __b) |
|
_mm_mask_max_ps
__m128 _mm_mask_max_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B) |
|
_mm_maskz_max_ps
__m128 _mm_maskz_max_ps(__mmask8 __U, __m128 __A, __m128 __B) |
|
_mm256_max_ps
__m256 _mm256_max_ps(__m256 __a, __m256 __b) |
|
_mm256_mask_max_ps
__m256 _mm256_mask_max_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B) |
|
_mm256_maskz_max_ps
__m256 _mm256_maskz_max_ps(__mmask8 __U, __m256 __A, __m256 __B) |
|
_mm512_max_ps
__m512 _mm512_max_ps(__m512 __A, __m512 __B) |
|
_mm512_max_round_ps
__m512 _mm512_max_round_ps(__m512 A, __m512 B, const int R) |
|
_mm512_mask_max_ps
__m512 _mm512_mask_max_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_mask_max_round_ps
__m512 _mm512_mask_max_round_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int R) |
|
_mm512_maskz_max_ps
__m512 _mm512_maskz_max_ps(__mmask16 __U, __m512 __A, __m512 __B) |
|
_mm512_maskz_max_round_ps
__m512 _mm512_maskz_max_round_ps(__mmask16 U, __m512 A, __m512 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
- VDIVPD
- VDIVPS
- VDIVSD
- VDIVSS
- VDPPD
- VDPPS
- VEXTRACTF128
- VEXTRACTPS
- VHADDPD
- VHADDPS
- VHSUBPD
- VHSUBPS
- VINSERTF128
- VINSERTPS
- VLDDQU
- VLDMXCSR
- VMASKMOVDQU
- VMASKMOVPD
- VMASKMOVPS
- VMAXPD
- VMAXSD
- VMAXSS
- VMINPD
- VMINPS
- VMINSD
- VMINSS
- VMOVAPD
- VMOVAPS
- VMOVD
- VMOVDDUP
- VMOVDQA
- VMOVDQU
- VMOVHLPS
- VMOVHPD
- VMOVHPS
- VMOVLHPS
- VMOVLPD
- VMOVLPS
- VMOVMSKPD
- VMOVMSKPS
More AVX10.1 instructions
- VGETMANTPD
- VGETMANTPH
- VGETMANTPS
- VGETMANTSD
- VGETMANTSH
- VGETMANTSS
- VGF2P8AFFINEINVQB
- VGF2P8AFFINEQB
- VGF2P8MULB
- VINSERTF32X4
- VINSERTF32X8
- VINSERTF64X2
- VINSERTF64X4
- VINSERTI32X4
- VINSERTI32X8
- VINSERTI64X2
- VINSERTI64X4
- VINSERTPS
- VMAXPD
- VMAXPH
- VMAXSD
- VMAXSH
- VMAXSS
- VMINPD
- VMINPH
- VMINPS
- VMINSD
- VMINSH
- VMINSS
- VMOVAPD
- VMOVAPS
- VMOVD
- VMOVDDUP
- VMOVDQA32
- VMOVDQA64
- VMOVDQU16
- VMOVDQU32
- VMOVDQU64
- VMOVDQU8
- VMOVHLPS
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-8 (MAXPS)
- 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.