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

VRANGEPD is VRANGEPS for doubles: for each pair it picks the smaller or the larger value, by value or by magnitude, as immediate bits 1:0 say, then sets the sign as bits 3:2 say, from the first source, from the chosen value, cleared or set. That page gives the useful immediates and the rules for zeros and NaNs. It came with AVX512DQ, together with the scalar VRANGESD. The SDM’s example for it is vrangepd zmm_dst, zmm_src, zmm_1023, 02h, which limits each double to the range -1023 to 1023 in one instruction: the smaller magnitude, with the sign of the input.

Recorded on Zen 5

  • The clamp. With immediate 02h, 3.0 against a bound of -4.0 gave 3.0 and -3.0 against 4.0 gave -3.0; -2.0 against 2.0 gave -2.0 and 2.0 against -2.0 gave 2.0, since of x and -x the smaller magnitude is -x and the sign then comes from the first source.
  • The sign set. Immediate 0Ch, the minimum with the sign set, gave -1.0 for 1.0 paired with itself.
  • Signaling NaNs. 1.0 against the broadcast signaling NaN 7FF0000000012345h gave the NaN quieted, 7FF8000000012345h, and set IE. The immediate was 1Ah, with bit 4 set, a bit the SDM says must be zero; Zen 5 did not fault.
  • DAZ. With DAZ set and immediate 02h, the largest denormal against 2^-1022 gave +0, and under immediate 06h the denormal 8008000000000000h against 1.0 gave -0, without DE.

In compiled code

At -O2 with -march=x86-64-v4, GCC 14 and Clang 23 emit VRANGEPD only for the intrinsics, such as _mm512_range_pd(a, b, 2). A loop of fmax becomes VMAXPD with a NaN fix-up in Clang, and a pick by magnitude with copysign becomes compares, VPTERNLOGQ and VBLENDMPD in GCC.

AMD’s Zen 5 latency spreadsheet gives every width one macro-op on pipe FP2 or FP3 and 2 cycles, two per cycle, as for VRANGEPS.

In the optimization guide

What the optimization guide says about VRANGEPD, a line per claim. Each links to the claim in the guide, with its sources and where they differ.

Golden Cove and Raptor Cove

Forms

Every encoding of VRANGEPD that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
VRANGEPD xmm {k}{z}, xmm, xmm, imm8 VRANGEPD_XMMf64_MASKmskw_XMMf64_XMMf64_IMM8_AVX512EVEX.128.66.0F3A.W1 50 /r ibAVX10.1 or AVX512DQ + AVX512VL
VRANGEPD xmm {k}{z}, xmm, m128/m64bcst, imm8 VRANGEPD_XMMf64_MASKmskw_XMMf64_MEMf64_IMM8_AVX512EVEX.128.66.0F3A.W1 50 /r ibAVX10.1 or AVX512DQ + AVX512VL
VRANGEPD ymm {k}{z}, ymm, ymm, imm8 VRANGEPD_YMMf64_MASKmskw_YMMf64_YMMf64_IMM8_AVX512EVEX.256.66.0F3A.W1 50 /r ibAVX10.1 or AVX512DQ + AVX512VL
VRANGEPD ymm {k}{z}, ymm, m256/m64bcst, imm8 VRANGEPD_YMMf64_MASKmskw_YMMf64_MEMf64_IMM8_AVX512EVEX.256.66.0F3A.W1 50 /r ibAVX10.1 or AVX512DQ + AVX512VL
VRANGEPD zmm {k}{z}, zmm, zmm, imm8, {sae} VRANGEPD_ZMMf64_MASKmskw_ZMMf64_ZMMf64_IMM8_AVX512EVEX.512.66.0F3A.W1 50 /r ibAVX10.1 or AVX512DQ
VRANGEPD zmm {k}{z}, zmm, m512/m64bcst, imm8 VRANGEPD_ZMMf64_MASKmskw_ZMMf64_MEMf64_IMM8_AVX512EVEX.512.66.0F3A.W1 50 /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
ymm {k}{z}, ymm, ymm, imm8
xmm {k}{z}, xmm, m128/m64bcst, imm8ymm {k}{z}, ymm, m256/m64bcst, imm8zmm {k}{z}, zmm, zmm, imm8, {sae}zmm {k}{z}, zmm, m512/m64bcst, imm8
Skylake-SP4 / 0.5p0110 / 0.5p0111 / 0.5p014 / 0.5p0511 / 0.5p05
Ice Lake4 / 0.5p0110 / 0.5p0111 / 0.5p014 / 1p011 / 1p0
Sapphire Rapids4 / 0.5p0111 / 0.5p0112 / 0.5p014 / 1p012 / 1p0
Zen 42 / 1FP0 FP110 / 0.5FP2 FP310 / 0.5FP2 FP32 / 1FP0 FP110 / 1FP2 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.

Element-wise: each double of the result comes from the double in the same place in each source.
VRANGEPD: element by elementResult double i comes from double i of xmm2 and xmm3. Result doubles 1 to 0: r1, r0.01xmm2a11k1r0r1xmm101xmm3or m128b

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 and xmm3. 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 = zmm2.f64[i]
        b = src3.f64[i]
        zmm1.f64[i] = frange(a, b, imm8)
    elif zeroing:
        zmm1.f64[i] = 0
    # else: zmm1.f64[i] keeps its value
# imm8[1:0]: min, max, min |x|, max |x|; [3:2]: sign of a, of the result, 0, 1
# m64bcst: src3.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
VRANGEPD xmm {k}{z}, xmm, xmm/m128/m64bcst, imm8 VRANGEPD ymm {k}{z}, ymm, ymm/m256/m64bcst, imm8 VRANGEPD zmm {k}{z}, zmm, zmm/m512/m64bcst, imm8, {sae}
xmm, ymm, zmmexplicitwrite (masked)
{k}explicitread (write mask)
xmm, ymm, zmmexplicitread
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 VRANGEPD, 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_range_pd __m128d _mm_range_pd(__m128d A, __m128d B, const int C)

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

_mm_mask_range_pd __m128d _mm_mask_range_pd(__m128d W, __mmask8 U, __m128d A, __m128d B, const int C)

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

_mm_maskz_range_pd __m128d _mm_maskz_range_pd(__mmask8 U, __m128d A, __m128d B, const int C)

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

_mm256_range_pd __m256d _mm256_range_pd(__m256d A, __m256d B, const int C)

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

_mm256_mask_range_pd __m256d _mm256_mask_range_pd(__m256d W, __mmask8 U, __m256d A, __m256d B, const int C)

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

_mm256_maskz_range_pd __m256d _mm256_maskz_range_pd(__mmask8 U, __m256d A, __m256d B, const int C)

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

_mm512_range_pd __m512d _mm512_range_pd(__m512d A, __m512d B, const int C)

VRANGEPD zmm, zmm, zmm, imm8 EVEX.512 -mavx512dq

_mm512_range_round_pd __m512d _mm512_range_round_pd(__m512d A, __m512d B, const int C, const int R)

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

_mm512_mask_range_pd __m512d _mm512_mask_range_pd(__m512d W, __mmask8 U, __m512d A, __m512d B, const int C)

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

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

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

_mm512_maskz_range_pd __m512d _mm512_maskz_range_pd(__mmask8 U, __m512d A, __m512d B, const int C)

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

_mm512_maskz_range_round_pd __m512d _mm512_maskz_range_round_pd(__mmask8 U, __m512d A, __m512d B, const int C, const int R)

VRANGEPD zmm {k}{z}, zmm, 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-661 (VRANGEPD)
  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.