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

VREDUCESS returns what rounding takes from the low single of its second source: x minus x rounded to a multiple of 2^-M, M being bits 7:4 of the immediate, while bits 3:0 choose the rounding direction, MXCSR’s mode instead, and no precision exception, as in VRNDSCALESS’s immediate. Bits 127:32 come from the first source, and a write mask decides only the low single. It is the scalar form of VREDUCEPS, whose page explains the range each rounding direction gives, the special results and the use in exp2 and pow; VREDUCESD is the double form and VREDUCESH the half-precision one. It came with AVX512DQ, takes an XMM register or 4 bytes of memory as its second source, and {sae} in the register form.

Recorded on Zen 5

  • A quiet NaN. vreducess xmm0{k2}{z}, xmm31, dword ptr [...], 0x18 returned the quiet NaN FFC00005h unchanged, without a flag, and the three singles above it came from XMM31.
  • Merging. With bit 0 of K1 clear, vreducess xmm24{k1}, xmm3, xmm3, {sae}, 0x22 kept the old low single of XMM24 and took the upper three from XMM3.

In compiled code

At -O2 with -march=x86-64-v4, GCC 14 and Clang 23 emit VREDUCESS only for the intrinsics, such as _mm_reduce_ss(a, b, 0x11). x - nearbyintf(x) rounds with VRNDSCALESS in GCC and VROUNDSS in Clang, then subtracts with VSUBSS.

AMD’s Zen 5 latency spreadsheet gives two macro-ops on pipes FP2 and FP3 and 6 cycles, one per cycle, and four macro-ops from memory, as for VREDUCESD.

Forms

Every encoding of VREDUCESS that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VREDUCESS xmm {k}{z}, xmm, xmm, imm8, {sae} VREDUCESS_XMMf32_MASKmskw_XMMf32_XMMf32_IMM8_AVX512EVEX.LIG.66.0F3A.W0 57 /r ibAVX10.1 or AVX512DQ
VREDUCESS xmm {k}{z}, xmm, m32, imm8 VREDUCESS_XMMf32_MASKmskw_XMMf32_MEMf32_IMM8_AVX512EVEX.LIG.66.0F3A.W0 57 /r ibAVX10.1 or AVX512DQ

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, imm8, {sae}xmm {k}{z}, xmm, m32, imm8
Skylake-SP, Ice Lake8 / 1p0114 / 1p01
Sapphire Rapids4 / 0.5p0111 / 0.5p01
Zen 46 / 3FP2 FP310 / 0.5FP2 FP3

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.
VREDUCESS: the low elementResult single 0 is computed from single 0 of 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 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]:
    xmm1.f32[0] = reduce(src3.f32[0], imm8)
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
# imm8[7:4]: fraction bits kept; [1:0]: rn, rd, ru, rz; bit 2: MXCSR.RC; bit 3: no PE
# xmm1 is zeroed from bit 128 up

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

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 VREDUCESS, 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_reduce_round_ss __m128 _mm_reduce_round_ss(__m128 A, __m128 B, const int C, const int R)

VREDUCESS xmm, xmm, xmm, imm8, {sae} EVEX.LIG -mavx512dq

_mm_reduce_ss __m128 _mm_reduce_ss(__m128 A, __m128 B, const int C)

VREDUCESS xmm, xmm, xmm, imm8 EVEX.LIG -mavx512dq

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

VREDUCESS xmm {k}, xmm, xmm, imm8, {sae} EVEX.LIG -mavx512dq

_mm_mask_reduce_ss __m128 _mm_mask_reduce_ss(__m128 W, __mmask8 U, __m128 A, __m128 B, const int C)

VREDUCESS xmm {k}, xmm, xmm, imm8 EVEX.LIG -mavx512dq

_mm_maskz_reduce_round_ss __m128 _mm_maskz_reduce_round_ss(__mmask8 U, __m128 A, __m128 B, const int C, const int R)

VREDUCESS xmm {k}{z}, xmm, xmm, imm8, {sae} EVEX.LIG -mavx512dq

_mm_maskz_reduce_ss __m128 _mm_maskz_reduce_ss(__mmask8 U, __m128 A, __m128 B, const int C)

VREDUCESS xmm {k}{z}, xmm, xmm, imm8 EVEX.LIG -mavx512dq

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
AVX512DQ_SCALAR

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

or

AVX512DQ
CPUID.(EAX=07H,ECX=0):EBX[17] AVX512DQ

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

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-697 (VREDUCESS)
  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.