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

VMAXSS is MAXSS in VEX and EVEX encodings: the larger of the low singles of its two sources, by the asymmetric rule that MINPS explains, with singles 1 to 3 copied from the first source and the bits above 127 cleared. The VEX form needs AVX, the EVEX form AVX-512F or AVX10.1, which adds a write mask on the low single and {sae} on xmm registers; VMAXPS shows what {sae} does to a signaling NaN. Zen 5’s recorded cases:

  • vmaxss xmm8, xmm15, xmm0, under MXCSR 3FC0H, returned +0 from XMM0 for -0 against +0, the second source as the rule says. The upper singles of XMM15 included the signaling NaN 7F812345H, which arrived unchanged, still signaling, and IE stayed clear: copied elements are not operands.
  • vmaxss xmm9{k1}{z}, xmm9, dword ptr [mem], with bit 0 of K1 clear, zeroed the low single, which held +infinity, and kept the three above it from XMM9.

The order of the operands

Only the last operand can be in memory, and the rule makes the order matter. In our builds with -march=x86-64-v3 or x86-64-v4, GCC 14 and Clang 23 compile a > b ? a : b to vmaxss xmm0, xmm0, xmm1, but the running maximum m = fa[i] > m ? fa[i] : m over a global array loads each element with VMOVSS and computes vmaxss xmm0, xmm1, xmm0: the element must be the first source, as it wins only when greater, so it cannot be read from memory in place.

For fmaxf, which must return the number when one argument is a NaN, GCC calls the library at both levels. Clang swaps the operands of VMAXSS and corrects the case of a NaN first argument with VCMPUNORDSS: through VBLENDVPS for x86-64-v3, and for x86-64-v4 through a mask register and a masked VMOVSS, an EVEX use of the write mask on a scalar.

AMD’s latency spreadsheet for Zen 5 lists it at 2 cycles on pipes FP2 and FP3. VMINSS is the minimum.

Forms

Every encoding of VMAXSS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMAXSS xmm, xmm, m32 VMAXSS_XMMdq_XMMdq_MEMdVEX.LIG.F3.0F.WIG 5F /rAVX
VMAXSS xmm, xmm, xmm VMAXSS_XMMdq_XMMdq_XMMdVEX.LIG.F3.0F.WIG 5F /rAVX
VMAXSS xmm {k}{z}, xmm, xmm, {sae} VMAXSS_XMMf32_MASKmskw_XMMf32_XMMf32_AVX512EVEX.LIG.F3.0F.W0 5F /rAVX10.1 or AVX512F
VMAXSS xmm {k}{z}, xmm, m32 VMAXSS_XMMf32_MASKmskw_XMMf32_MEMf32_AVX512EVEX.LIG.F3.0F.W0 5F /rAVX10.1 or AVX512F

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, m32
xmm {k}{z}, xmm, m32
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm, {sae}
Sandy Bridge9 / 1p13 / 1p1
Haswell, Broadwell8 / 1p13 / 1p1
Skylake, Skylake-SP, Ice Lake9 / 0.5p014 / 0.5p01
Alder Lake, Sapphire Rapids11 / 0.5p014 / 0.5p01
Lunar Lake10 / 2V0 V14 / 2V0 V1
Piledriver7 / 1.5FPFMA FPU02 / 1FPFMA FPU0
Zen, Zen 28 / 0.5FPU0 FPU11 / 0.5FPU0 FPU1
Zen 38 / 0.5FP0 FP11 / 0.5FP0 FP1
Zen 49 / 1FP0 FP12 / 11FP0 FP1
Jaguar7 / 1FPA FPU02 / 1FPA FPU0
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 0.5 for Zen 4 and Zen 5 (AMD 57647, row 1560; AMD 58455, row 1087).

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.

Scalar: only the low single is computed; the other singles come from xmm2.
VMAXSS: the low elementResult single 0 is computed from single 0 of xmm2 and xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: a3, a2, a1, r0.0123xmm2a1k1r0a1a2a3xmm10123xmm3or m32b

The write mask k1 applies to the low single: with bit 0 clear it keeps its old value, or is zeroed with {z}.

Result single 0 is computed from single 0 of xmm2 and xmm3; singles 3 to 1 are those of xmm2. Result singles 3 to 0: a3, a2, a1, r0.

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

if k1[0]:  # 1 without a write mask
    a = xmm2.f32[0]
    b = src3.f32[0]
    xmm1.f32[0] = fmax(a, b)
elif zeroing:
    xmm1.f32[0] = 0
# else: xmm1.f32[0] keeps its value
for i in range(1, 4):
    xmm1.d[i] = xmm2.d[i]
# {sae}: no exception flags
# a NaN or two zeros: b
# xmm1 is zeroed from bit 128 up

Run on AMD Zen 5 (EPYC 9645): 6 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
VMAXSS xmm, xmm, xmm/m32
xmmexplicitwrite
xmmexplicitread
xmm/m32explicitread
VMAXSS xmm {k}{z}, xmm, xmm/m32, {sae}
xmmexplicitwrite (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m32explicitread

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-3
EVEX forms
AVX512-E3

Attributes

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

All forms
follows MXCSR
EVEX forms
write masking
EVEX memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VMAXSS, 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_round_ss __m128 _mm_max_round_ss(__m128 A, __m128 B, const int R)

VMAXSS xmm, xmm, xmm, {sae} EVEX.LIG -mavx512f

_mm_max_ss __m128 _mm_max_ss(__m128 __a, __m128 __b)

VMAXSS xmm, xmm, xmm VEX.LIG -mavxwith AVX enabled

_mm_mask_max_round_ss __m128 _mm_mask_max_round_ss(__m128 W, __mmask8 U, __m128 A, __m128 B, const int R)

VMAXSS xmm {k}, xmm, xmm, {sae} EVEX.LIG -mavx512f

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

VMAXSS xmm {k}, xmm, xmm EVEX.LIG -mavx512f

_mm_maskz_max_round_ss __m128 _mm_maskz_max_round_ss(__mmask8 U, __m128 A, __m128 B, const int R)

VMAXSS xmm {k}{z}, xmm, xmm, {sae} EVEX.LIG -mavx512f

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

VMAXSS xmm {k}{z}, xmm, xmm EVEX.LIG -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.

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-13 (MAXSS)
  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. 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.