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

VREDUCEPD returns, for each double x, x minus x rounded to M fraction bits, M being bits 7:4 of the immediate: what rounding takes away. It is the double form of VREDUCEPS, whose page shows how the rounding direction sets the range of the result and how the result and VRNDSCALEPD’s add up to x. Like it, it needs AVX512DQ, takes a mask, a broadcast and, at 512 bits, {sae}, and the scalar form is VREDUCESD.

Recorded on Zen 5

  • Halves. With immediate 18h, M = 1 and rounding to nearest without a precision exception, x keeps what lies beyond a multiple of 1/2: 41DFFFFFFFFFFFFFh, 2^31 - 2^-22, gave -2^-22, as it rounds up to 2^31; 0.1 came back unchanged, as it rounds to 0; -2.5 and 2^31 - 1 gave 0.
  • Zeros and infinities. +infinity gave +0 with immediate 10h, and -0 gave +0 with F8h, M = 15 rounding to nearest, the same as the single cases on VREDUCEPS’s page. No case changed MXCSR.

In compiled code

GCC 14 and Clang 23 at -O2 emit VREDUCEPD only for the intrinsics, such as _mm512_reduce_pd(x, imm). A loop of a[i] - nearbyint(a[i]) over double arrays, with -march=x86-64-v4, is VRNDSCALEPD and VSUBPD in GCC and VROUNDPD and VSUBPD on YMM registers in Clang; a[i] - floor(a[i]) stays scalar VRNDSCALESD in GCC unless -ffast-math is given, and for infinities none of these equals VREDUCEPD’s +0.

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

Forms

Every encoding of VREDUCEPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VREDUCEPD xmm {k}{z}, xmm, imm8 VREDUCEPD_XMMf64_MASKmskw_XMMf64_IMM8_AVX512EVEX.128.66.0F3A.W1 56 /r ibAVX10.1 or AVX512DQ + AVX512VL
VREDUCEPD xmm {k}{z}, m128/m64bcst, imm8 VREDUCEPD_XMMf64_MASKmskw_MEMf64_IMM8_AVX512EVEX.128.66.0F3A.W1 56 /r ibAVX10.1 or AVX512DQ + AVX512VL
VREDUCEPD ymm {k}{z}, ymm, imm8 VREDUCEPD_YMMf64_MASKmskw_YMMf64_IMM8_AVX512EVEX.256.66.0F3A.W1 56 /r ibAVX10.1 or AVX512DQ + AVX512VL
VREDUCEPD ymm {k}{z}, m256/m64bcst, imm8 VREDUCEPD_YMMf64_MASKmskw_MEMf64_IMM8_AVX512EVEX.256.66.0F3A.W1 56 /r ibAVX10.1 or AVX512DQ + AVX512VL
VREDUCEPD zmm {k}{z}, zmm, imm8, {sae} VREDUCEPD_ZMMf64_MASKmskw_ZMMf64_IMM8_AVX512EVEX.512.66.0F3A.W1 56 /r ibAVX10.1 or AVX512DQ
VREDUCEPD zmm {k}{z}, m512/m64bcst, imm8 VREDUCEPD_ZMMf64_MASKmskw_MEMf64_IMM8_AVX512EVEX.512.66.0F3A.W1 56 /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, imm8xmm {k}{z}, m128/m64bcst, imm8ymm {k}{z}, ymm, imm8ymm {k}{z}, m256/m64bcst, imm8zmm {k}{z}, zmm, imm8, {sae}zmm {k}{z}, m512/m64bcst, imm8
Skylake-SP, Ice Lake8 / 1p0114 / 1p018 / 1p0115 / 1p018 / 1p0515 / 1p05
Sapphire Rapids4 / 0.5p0111 / 0.5p014 / 0.5p0112 / 0.5p014 / 1p012 / 1p0
Zen 46 / 31FP2 FP310 / 0.5FP2 FP33 / 0.52FP2 FP310 / 0.5FP2 FP36 / 3FP2 FP310 / 1FP2 FP3
  1. Zen 4 model: AMD's spreadsheets give reciprocal throughput 1 for Zen 4 and Zen 5 (AMD 57647, row 3207; AMD 58455, row 886).
  2. Zen 4 model: AMD's spreadsheets give latency 6 for Zen 4 and Zen 5 (AMD 57647, row 3209; AMD 58455, row 886).

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 double of the result comes from the double in the same place in each source.
VREDUCEPD: element by elementResult double i comes from double i of xmm2. Result doubles 1 to 0: r1, r0.01xmm2or m128a11k1r0r1xmm1

Every double works alike: 2, 4 and 8 doubles in the xmm, ymm and zmm forms. The forms write under a mask: where its bit is 0, the element keeps its old value, or zeroes it with {z}. With m64bcst, one double from memory stands for every element of the last source.

Result double i comes from double i of xmm2. Result doubles 1 to 0: 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(VL // 64):
    if k1[i]:
        a = src2.f64[i]
        zmm1.f64[i] = reduce(a, imm8)
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[i] keeps its value
# imm8[7:4]: fraction bits kept; [1:0]: rn, rd, ru, rz; bit 2: MXCSR.RC; bit 3: no PE
# m64bcst: src2.f64[i] is the m64 for every i
# {sae}: no exception flags
# zmm1 is zeroed from bit VL up

Run on AMD Zen 5 (EPYC 9645): 9 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
VREDUCEPD xmm {k}{z}, xmm/m128/m64bcst, imm8 VREDUCEPD ymm {k}{z}, ymm/m256/m64bcst, imm8 VREDUCEPD zmm {k}{z}, zmm/m512/m64bcst, imm8, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm/m128/m64bcst, ymm/m256/m64bcst, zmm/m512/m64bcstexplicitread
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-E2

Attributes

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

All forms
write masking; follows MXCSR
Memory forms
embedded broadcast (tuple Full); memory fault suppression

Intrinsics

The C intrinsics of Clang 23.1.2 that compile to VREDUCEPD, 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_pd __m128d _mm_reduce_pd(__m128d A, const int B)

VREDUCEPD xmm, xmm, imm8 EVEX.128 -mavx512vl -mavx512dq

_mm_mask_reduce_pd __m128d _mm_mask_reduce_pd(__m128d W, __mmask8 U, __m128d A, const int B)

VREDUCEPD xmm {k}, xmm, imm8 EVEX.128 -mavx512vl -mavx512dq

_mm_maskz_reduce_pd __m128d _mm_maskz_reduce_pd(__mmask8 U, __m128d A, const int B)

VREDUCEPD xmm {k}{z}, xmm, imm8 EVEX.128 -mavx512vl -mavx512dq

_mm256_reduce_pd __m256d _mm256_reduce_pd(__m256d A, const int B)

VREDUCEPD ymm, ymm, imm8 EVEX.256 -mavx512vl -mavx512dq

_mm256_mask_reduce_pd __m256d _mm256_mask_reduce_pd(__m256d W, __mmask8 U, __m256d A, const int B)

VREDUCEPD ymm {k}, ymm, imm8 EVEX.256 -mavx512vl -mavx512dq

_mm256_maskz_reduce_pd __m256d _mm256_maskz_reduce_pd(__mmask8 U, __m256d A, const int B)

VREDUCEPD ymm {k}{z}, ymm, imm8 EVEX.256 -mavx512vl -mavx512dq

_mm512_reduce_pd __m512d _mm512_reduce_pd(__m512d A, const int B)

VREDUCEPD zmm, zmm, imm8 EVEX.512 -mavx512dq

_mm512_reduce_round_pd __m512d _mm512_reduce_round_pd(__m512d A, const int B, const int R)

VREDUCEPD zmm, zmm, imm8, {sae} EVEX.512 -mavx512dq

_mm512_mask_reduce_pd __m512d _mm512_mask_reduce_pd(__m512d W, __mmask8 U, __m512d A, const int B)

VREDUCEPD zmm {k}, zmm, imm8 EVEX.512 -mavx512dq

_mm512_mask_reduce_round_pd __m512d _mm512_mask_reduce_round_pd(__m512d W, __mmask8 U, __m512d A, const int B, const int R)

VREDUCEPD zmm {k}, zmm, imm8, {sae} EVEX.512 -mavx512dq

_mm512_maskz_reduce_pd __m512d _mm512_maskz_reduce_pd(__mmask8 U, __m512d A, const int B)

VREDUCEPD zmm {k}{z}, zmm, imm8 EVEX.512 -mavx512dq

_mm512_maskz_reduce_round_pd __m512d _mm512_maskz_reduce_round_pd(__mmask8 U, __m512d A, const int B, const int R)

VREDUCEPD zmm {k}{z}, zmm, imm8, {sae} EVEX.512 -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_128

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

or

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

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
AVX512DQ_256
Same as AVX512DQ_128Same as AVX512DQ_128
AVX512DQ_512

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

Same as AVX512DQ_128

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-685 (VREDUCEPD)
  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.