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

VMAXSD is MAXSD in VEX and EVEX encodings: the larger of the low doubles of its two sources, returning the second source for a NaN in either or for two zeros, with the high double copied from the first source and the bits above 127 cleared. MAXSD’s page covers the rule and C’s idioms for it. The VEX form needs AVX, the EVEX form AVX-512F or AVX10.1, which adds a write mask on the low double and {sae}; there is no wider form. VMAXSS is the single version and shows why the operand order decides where memory can go. Zen 5’s recorded cases:

  • vmaxsd xmm8, xmm15, qword ptr [mem], under MXCSR 7F80H (round toward zero, DAZ clear), compared the largest denormal with the smallest normal double, returned the normal one and set DE, which a maximum reports for a denormal operand while DAZ is clear.
  • vmaxsd xmm1{k3}, xmm2, xmm3, {sae}, with bit 0 of K3 set, under 1E40H, where the invalid exception is unmasked, compared the quiet NaNs 7FF8000000000000H and FFF8000000000000H and returned the second with no #XM and IE still clear, though the maximum treats a quiet NaN as invalid. The high double, 1.0, came from XMM2.

From C

In our builds at -O2 with -march=x86-64-v3 and x86-64-v4, GCC 14 and Clang 23 compile a > b ? a : b over doubles to vmaxsd xmm0, xmm0, xmm1, and the running maximum of a global array to a VMOVSD load and vmaxsd xmm0, xmm1, xmm0, the element first, as on VMAXSS’s page. fmax is a library call in GCC; Clang swaps the operands and repairs a NaN first argument with VCMPUNORDSD, through VBLENDVPD at -v3 and through K1 and a masked VMOVSD at -v4. The EVEX features come from intrinsics: _mm_max_round_sd(a, b, _MM_FROUND_NO_EXC) is vmaxsd xmm0, xmm0, xmm1, {sae} and _mm_mask_max_sd a KMOV and a merging VMAXSD.

AMD’s latency spreadsheet for Zen 5 gives the VEX and the EVEX rows one macro-op of 2 cycles on pipes FP2 and FP3, two per cycle. VMINSD is the minimum.

Forms

Every encoding of VMAXSD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMAXSD xmm, xmm, m64 VMAXSD_XMMdq_XMMdq_MEMqVEX.LIG.F2.0F.WIG 5F /rAVX
VMAXSD xmm, xmm, xmm VMAXSD_XMMdq_XMMdq_XMMqVEX.LIG.F2.0F.WIG 5F /rAVX
VMAXSD xmm {k}{z}, xmm, xmm, {sae} VMAXSD_XMMf64_MASKmskw_XMMf64_XMMf64_AVX512EVEX.LIG.F2.0F.W1 5F /rAVX10.1 or AVX512F
VMAXSD xmm {k}{z}, xmm, m64 VMAXSD_XMMf64_MASKmskw_XMMf64_MEMf64_AVX512EVEX.LIG.F2.0F.W1 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, m64
xmm {k}{z}, xmm, m64
xmm, xmm, xmm
xmm {k}{z}, xmm, xmm, {sae}no mask, with a mask, zeroing
xmm {k}{z}, xmm, xmm, {sae}with {sae}
Sandy Bridge9 / 1p13 / 1p1
Haswell, Broadwell8 / 1p13 / 1p1
Skylake9 / 0.5p014 / 0.5p01
Skylake-SP, Ice Lake9 / 0.5p014 / 0.5p014 / 0.5p01
Alder Lake11 / 0.5p014 / 0.5p01
Sapphire Rapids11 / 0.5p014 / 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 48 / 0.5FP0 FP12 / 11FP0 FP11 / 0.52FP0 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 1558; AMD 58455, row 1086).
  2. Zen 4 model: AMD's spreadsheets give latency 2 for Zen 4 and Zen 5 (AMD 57647, row 1559; AMD 58455, row 129).

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 double is computed; the other double comes from xmm2.
VMAXSD: the low elementResult double 0 is computed from double 0 of xmm2 and xmm3; double 1 is that of xmm2. Result doubles 1 to 0: a1, r0.01xmm2a1k1r0a1xmm101xmm3or m64b

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

Result double 0 is computed from double 0 of xmm2 and xmm3; double 1 is that of xmm2. Result doubles 1 to 0: 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.f64[0]
    b = src3.f64[0]
    xmm1.f64[0] = fmax(a, b)
elif zeroing:
    xmm1.f64[0] = 0
# else: xmm1.f64[0] keeps its value
xmm1.q[1] = xmm2.q[1]
# {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
VMAXSD xmm, xmm, xmm/m64
xmmexplicitwrite
xmmexplicitread
xmm/m64explicitread
VMAXSD xmm {k}{z}, xmm, xmm/m64, {sae}
xmmexplicitwrite (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m64explicitread

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 VMAXSD, 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_sd __m128d _mm_max_round_sd(__m128d A, __m128d B, const int R)

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

_mm_max_sd __m128d _mm_max_sd(__m128d __a, __m128d __b)

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

_mm_mask_max_round_sd __m128d _mm_mask_max_round_sd(__m128d W, __mmask8 U, __m128d A, __m128d B, const int R)

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

_mm_mask_max_sd __m128d _mm_mask_max_sd(__m128d __W, __mmask8 __U, __m128d __A, __m128d __B)

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

_mm_maskz_max_round_sd __m128d _mm_maskz_max_round_sd(__mmask8 U, __m128d A, __m128d B, const int R)

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

_mm_maskz_max_sd __m128d _mm_maskz_max_sd(__mmask8 __U, __m128d __A, __m128d __B)

VMAXSD 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-11 (MAXSD)
  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.