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

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

Every encoding of VMAXPS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMAXPS xmm, xmm, m128 VMAXPS_XMMdq_XMMdq_MEMdqVEX.128.NP.0F.WIG 5F /rAVX
VMAXPS xmm, xmm, xmm VMAXPS_XMMdq_XMMdq_XMMdqVEX.128.NP.0F.WIG 5F /rAVX
VMAXPS ymm, ymm, m256 VMAXPS_YMMqq_YMMqq_MEMqqVEX.256.NP.0F.WIG 5F /rAVX
VMAXPS ymm, ymm, ymm VMAXPS_YMMqq_YMMqq_YMMqqVEX.256.NP.0F.WIG 5F /rAVX
VMAXPS zmm {k}{z}, zmm, zmm, {sae} VMAXPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_AVX512EVEX.512.NP.0F.W0 5F /rAVX10.1 or AVX512F
VMAXPS zmm {k}{z}, zmm, m512/m32bcst VMAXPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_AVX512EVEX.512.NP.0F.W0 5F /rAVX10.1 or AVX512F
VMAXPS xmm {k}{z}, xmm, xmm VMAXPS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.128.NP.0F.W0 5F /rAVX10.1 or AVX512F + AVX512VL
VMAXPS xmm {k}{z}, xmm, m128/m32bcst VMAXPS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.128.NP.0F.W0 5F /rAVX10.1 or AVX512F + AVX512VL
VMAXPS ymm {k}{z}, ymm, ymm VMAXPS_YMMf32_MASKmskw_YMMf32_YMMf32_AVX512EVEX.256.NP.0F.W0 5F /rAVX10.1 or AVX512F + AVX512VL
VMAXPS ymm {k}{z}, ymm, m256/m32bcst VMAXPS_YMMf32_MASKmskw_YMMf32_MEMf32_AVX512EVEX.256.NP.0F.W0 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/m32bcst
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm
ymm {k}{z}, ymm, ymm
ymm, ymm, m256
ymm {k}{z}, ymm, m256/m32bcst
ymm, ymm, ymmzmm {k}{z}, zmm, zmm, {sae}zmm {k}{z}, zmm, m512/m32bcst
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.5p05
Alder Lake11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p01
Sapphire Rapids11 / 0.5p014 / 0.5p0112 / 0.5p014 / 0.5p014 / 1p012 / 1p0
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 FP1
Jaguar7 / 1FPA FPU02 / 1FPA FPU07 / 2FPA FPU02 / 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.

Element-wise: each single of the result comes from the single in the same place in each source.
VMAXPS: element by elementResult 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.0123xmm2a1110k1r0r1r3xmm10123xmm3or m128b

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 up

Run on AMD Zen 5 (EPYC 9645): 45 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
VMAXPS xmm, xmm, xmm/m128 VMAXPS ymm, ymm, ymm/m256
xmm, ymmexplicitwrite
xmm, ymmexplicitread
xmm/m128, ymm/m256explicitread
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, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcstexplicitread

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.

IntrinsicCompiles to
_mm_max_ps __m128 _mm_max_ps(__m128 __a, __m128 __b)

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

_mm_mask_max_ps __m128 _mm_mask_max_ps(__m128 __W, __mmask8 __U, __m128 __A, __m128 __B)

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

_mm_maskz_max_ps __m128 _mm_maskz_max_ps(__mmask8 __U, __m128 __A, __m128 __B)

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

_mm256_max_ps __m256 _mm256_max_ps(__m256 __a, __m256 __b)

VMAXPS ymm, ymm, ymm VEX.256 -mavx

_mm256_mask_max_ps __m256 _mm256_mask_max_ps(__m256 __W, __mmask8 __U, __m256 __A, __m256 __B)

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

_mm256_maskz_max_ps __m256 _mm256_maskz_max_ps(__mmask8 __U, __m256 __A, __m256 __B)

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

_mm512_max_ps __m512 _mm512_max_ps(__m512 __A, __m512 __B)

VMAXPS zmm, zmm, zmm EVEX.512 -mavx512f

_mm512_max_round_ps __m512 _mm512_max_round_ps(__m512 A, __m512 B, const int R)

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

_mm512_mask_max_ps __m512 _mm512_mask_max_ps(__m512 __W, __mmask16 __U, __m512 __A, __m512 __B)

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

_mm512_mask_max_round_ps __m512 _mm512_mask_max_round_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int R)

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

_mm512_maskz_max_ps __m512 _mm512_maskz_max_ps(__mmask16 __U, __m512 __A, __m512 __B)

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

_mm512_maskz_max_round_ps __m512 _mm512_maskz_max_round_ps(__mmask16 U, __m512 A, __m512 B, const int R)

VMAXPS 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-8 (MAXPS)
  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.