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

VMAXSH is the scalar form of VMAXPH: the larger of the low halves of its two sources, the first returned only when it is greater than the second, with bits 127:16 copied from the first source and the bits above 127 cleared. It shares everything else with VMINSH: EVEX map 5 (opcode 5Fh with F3), a write mask on the low half, {sae} and a two-byte memory operand. VMAXSS is the single-precision form, and VADDPH covers the format.

Clamping a half

x = x < 0 ? 0 : x; x = x > 1 ? 1 : x; on one _Float16 shows the two compilers apart. In our builds at -O2 with -march=x86-64-v4 -mavx512fp16, Clang 23 emits VMAXSH with the zero as first source and then VMINSH with 1 as first source, so a NaN in x is the second source both times and comes out as a NaN, as the C code says. GCC 14 tests the lower bound with VCOMISH and a branch, and the upper one with VCMPSH into a mask register and a masked VMOVSH that puts 1 where x is greater, without VMINSH.

With one operand in memory the order of the operands decides again: x > *p ? x : *p becomes vmaxsh xmm0, xmm0, word ptr [rdi] in Clang, the half from memory being the second source, while GCC loads it first with VMOVW. A minimum converted to float is VMINSH followed by VCVTSH2SS in both.

AMD’s Zen 5 guide does not list AVX512-FP16, and this site’s recorded cases include none of VMAXSH.

Forms

Every encoding of VMAXSH that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VMAXSH xmm {k}{z}, xmm, xmm, {sae} VMAXSH_XMMf16_MASKmskw_XMMf16_XMMf16_AVX512EVEX.LIG.F3.MAP5.W0 5F /rAVX10.1 or AVX512_FP16
VMAXSH xmm {k}{z}, xmm, m16 VMAXSH_XMMf16_MASKmskw_XMMf16_MEMf16_AVX512EVEX.LIG.F3.MAP5.W0 5F /rAVX10.1 or AVX512_FP16

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 {k}{z}, xmm, xmm, {sae}no mask, with {sae}xmm {k}{z}, xmm, xmm, {sae}with a mask, zeroingxmm {k}{z}, xmm, m16
Sapphire Rapids5 / 0.5p016 / 0.5p0112 / 0.5p01

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 half is computed; the other halves come from xmm2.
VMAXSH: the low elementResult half 0 is computed from half 0 of xmm2 and xmm3; halves 7 to 1 are those of xmm2. Result halves 7 to 0: a7, a6, a5, a4, a3, a2, a1, r0.01234567xmm2a1k1r0a1a2a3a4a5a6a7xmm101234567xmm3or m16b

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

Result half 0 is computed from half 0 of xmm2 and xmm3; halves 7 to 1 are those of xmm2. Result halves 7 to 0: a7, a6, a5, a4, 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]:
    a = xmm2.f16[0]
    b = src3.f16[0]
    xmm1.f16[0] = fmax(a, b)
elif zeroing:
    xmm1.f16[0] = 0
# else: xmm1.f16[0] keeps its value
for i in range(1, 8):
    xmm1.w[i] = xmm2.w[i]
# {sae}: no exception flags
# a NaN or two zeros: b
# xmm1 is zeroed from bit 128 up

Not run on a processor: none of these processors has AVX512-FP16.

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
VMAXSH xmm {k}{z}, xmm, xmm/m16, {sae}
xmmexplicitwrite (masked)
{k}explicitread (write mask)
xmmexplicitread
xmm/m16explicitread

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.

All forms
AVX512-E3

Attributes

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

All forms
write masking; follows MXCSR
Memory forms
memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VMAXSH, 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_sh __m128h _mm_max_round_sh(__m128h A, __m128h B, const int R)

VMAXSH xmm, xmm, xmm, {sae} EVEX.LIG -mavx512fp16

_mm_max_sh __m128h _mm_max_sh(__m128h __A, __m128h __B)

VMAXSH xmm, xmm, xmm EVEX.LIG -mavx512fp16

_mm_mask_max_round_sh __m128h _mm_mask_max_round_sh(__m128h W, __mmask8 U, __m128h A, __m128h B, const int R)

VMAXSH xmm {k}, xmm, xmm, {sae} EVEX.LIG -mavx512fp16

_mm_mask_max_sh __m128h _mm_mask_max_sh(__m128h __W, __mmask8 __U, __m128h __A, __m128h __B)

VMAXSH xmm {k}, xmm, xmm EVEX.LIG -mavx512fp16

_mm_maskz_max_round_sh __m128h _mm_maskz_max_round_sh(__mmask8 U, __m128h A, __m128h B, const int R)

VMAXSH xmm {k}{z}, xmm, xmm, {sae} EVEX.LIG -mavx512fp16

_mm_maskz_max_sh __m128h _mm_maskz_max_sh(__mmask8 __U, __m128h __A, __m128h __B)

VMAXSH xmm {k}{z}, xmm, xmm EVEX.LIG -mavx512fp16

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
AVX512_FP16_SCALAR

AVX10.1
CPUID.(EAX=07H,ECX=1):EDX[19] AVX10
CPUID.(EAX=24H,ECX=0):EBX[7:0] ≥ 1 AVX10 version

or

AVX512_FP16
CPUID.(EAX=07H,ECX=0):EDX[23] AVX512_FP16

Nova Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, Diamond Rapids, Zen 6

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 Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
  6. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-421 (VMAXSH)
  7. 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.