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

PMINUW keeps the smaller of each pair of words, compared as unsigned 16-bit integers: 8 results in an XMM register. It came with SSE4.1, part of x86-64-v2, and has no MMX form. SSE2 could take the minimum of signed words only, with PMINSW, whose page shows the saturating subtraction that stood in for unsigned words before PMINUW existed. On Zen 5, the recorded pminuw xmm1, xmmword ptr [mem] kept 7FFFh over 8000h, where the signed PMINSW would have kept 8000h (-32768, the smaller signed value there), and left bits 255:128 of the register as they were, as legacy SSE instructions do (see mixing SSE and AVX).

What the legacy form adds

The destination doubles as the first source, and the second operand is an XMM register or a 128-bit memory location that must be aligned to 16 bytes. In our builds at -O2 over fixed-size uint16_t arrays, the plain C minimum compiles to the saturating-subtraction detour PMINSW’s page describes at the baseline, in GCC 14 and Clang 23 alike; with -march=x86-64-v2, both compilers replace it with one PMINUW per 8 words.

AMD’s latency spreadsheet for Zen 5 gives PMINUW one cycle, four per cycle, on any of the four vector pipelines.

Forms

Every encoding of PMINUW that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
PMINUW xmm, m128 PMINUW_XMMdq_MEMdq66 0F 38 3A /rSSE4.1
PMINUW xmm, xmm PMINUW_XMMdq_XMMdq66 0F 38 3A /rSSE4.1

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 word of the result comes from the word in the same place in each source.
PMINUW: element by elementResult word i comes from word i of xmm1 and xmm2. Result words 7 to 0: r7, r6, r5, r4, r3, r2, r1, r0.01234567xmm1ar0r1r2r3r4r5r6r7xmm101234567xmm2or m128b

Result word i comes from word i of xmm1 and xmm2. Result words 7 to 0: r7, r6, r5, r4, r3, r2, 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(8):
    xmm1.w[i] = min(xmm1.w[i], src2.w[i])
# bits 128 and up of the register are unchanged

Run on AMD Zen 5 (EPYC 9645): 2 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
PMINUW xmm, xmm/m128
xmmexplicitread, write
xmm/m128explicitread

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
SSE_TYPE_4

Attributes

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

Memory forms
aligned memory operand

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to PMINUW, 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_min_epu16 __m128i _mm_min_epu16(__m128i __V1, __m128i __V2)

PMINUW xmm, xmm Legacy -msse4.1

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
SSE4

SSE4.1
CPUID.01H:ECX[19] SSE4.1

Penryn, Nehalem, Westmere, 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, Silvermont, Goldmont, Goldmont Plus, Tremont, Snow Ridge, Lakefield, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, K10 (Family 10h), Bulldozer, Piledriver, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6

Note: XED's AMD_K10 inherits everything from its Westmere chip, including SSSE3, SSE4.1, SSE4.2, AES-NI and PCLMULQDQ; GCC's -march=amdfam10 has none of them.

More SSE4.1 instructions

All 49 SSE4.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. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-341 (PMINUB/PMINUW)
  5. 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, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.