Instruction
VRANGEPS
Computes the minimum, maximum, or value of smaller or larger magnitude of packed singles, as an immediate selects along with the sign of the result.
- Extensions
- Forms
- 6 (6 EVEX)
- Data
- Intel XED v2026.08.23
VRANGEPS picks, for each pair of singles, the smaller or the larger, by value or by magnitude, and then sets the sign of the result. Bits 1:0 of the immediate choose the comparison: minimum, maximum, minimum of the absolute values or maximum of the absolute values. Bits 3:2 choose the sign: that of the first source (00), that of the chosen value (01), cleared (10) or set (11). It came with AVX512DQ, together with VRANGEPD and the scalar VRANGESS and VRANGESD; AVX10.2’s VMINMAXPS uses the same sign field.
Useful immediates
| imm8 | Result |
|---|---|
| 04h, 05h | min(a, b), max(a, b) |
| 0Ah, 0Bh | min(|a|, |b|), max(|a|, |b|) |
| 02h | a clamped to [-|b|, |b|] |
| 0Eh | -min(|a|, |b|) |
The trap is that 00h and 01h are not plain minimum and maximum: they keep the sign of the first source. In a case recorded on Zen 5, immediate 01h on -2 and 1 gave -1: the maximum, 1, with the sign of -2. With 02h and a bound in b, a is limited to a symmetric range in one instruction.
Zeros and NaNs
Unlike MINPS and MAXPS, which return
their second source for a NaN or two zeros, VRANGEPS treats both orders
alike. -0 counts as less than +0, whichever operand holds it; and for
the magnitude comparisons, of x and -x the minimum is -x and the maximum
x. A quiet NaN loses to a number, as in IEEE 754-2008’s minNum; a
signaling NaN is returned quieted and sets the invalid flag, and then
the sign field is ignored. Zen 5 turned 7F812345h against 1.0 into
7FC12345h and set IE, and 7FC12345h against 1.0 into 1.0. A denormal
input sets DE, or counts as a zero under DAZ; {sae} suppresses the
flags.
In compiled code
GCC 14 and Clang 23 emit VRANGEPS only for the intrinsics, such as
_mm512_range_ps(a, b, imm), with AVX512DQ enabled (x86-64-v4 has
it). Loops of fmaxf, of a clamp with copysignf or of a pick by
magnitude become compares, blends and VPTERNLOGD
instead.
Intel’s optimization manual counts VRANGE among the instructions that wait for the old value of their destination on Golden Cove, and recommends zeroing that register first (Section 2.4.1.2). AMD’s Zen 5 guide lists VRANGEPS as one macro-op with a latency of 2 cycles, the same as VMAXPS.
In the optimization guide
What the optimization guide says about VRANGEPS, a line per claim. Each links to the claim in the guide, with its sources and where they differ.
Golden Cove and Raptor Cove
- Vectors, AVX-512 and AMX: VPERMD, VPERMQ, VPERMPS, VPERMPD, VPMULLQ,
vrange,vgetmantand the half-precision complex multiplications wait for the old value of their destination, which they then overwrite.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
VRANGEPS xmm {k}{z}, xmm, xmm, imm8
VRANGEPS_XMMf32_MASKmskw_XMMf32_XMMf32_IMM8_AVX512 | EVEX.128.66.0F3A.W0 50 /r ib | AVX10.1 or AVX512DQ + AVX512VL |
VRANGEPS xmm {k}{z}, xmm, m128/m32bcst, imm8
VRANGEPS_XMMf32_MASKmskw_XMMf32_MEMf32_IMM8_AVX512 | EVEX.128.66.0F3A.W0 50 /r ib | AVX10.1 or AVX512DQ + AVX512VL |
VRANGEPS ymm {k}{z}, ymm, ymm, imm8
VRANGEPS_YMMf32_MASKmskw_YMMf32_YMMf32_IMM8_AVX512 | EVEX.256.66.0F3A.W0 50 /r ib | AVX10.1 or AVX512DQ + AVX512VL |
VRANGEPS ymm {k}{z}, ymm, m256/m32bcst, imm8
VRANGEPS_YMMf32_MASKmskw_YMMf32_MEMf32_IMM8_AVX512 | EVEX.256.66.0F3A.W0 50 /r ib | AVX10.1 or AVX512DQ + AVX512VL |
VRANGEPS zmm {k}{z}, zmm, zmm, imm8, {sae}
VRANGEPS_ZMMf32_MASKmskw_ZMMf32_ZMMf32_IMM8_AVX512 | EVEX.512.66.0F3A.W0 50 /r ib | AVX10.1 or AVX512DQ |
VRANGEPS zmm {k}{z}, zmm, m512/m32bcst, imm8
VRANGEPS_ZMMf32_MASKmskw_ZMMf32_MEMf32_IMM8_AVX512 | EVEX.512.66.0F3A.W0 50 /r ib | AVX10.1 or AVX512DQ |
Latency and throughput
| Model | xmm {k}{z}, xmm, xmm, imm8ymm {k}{z}, ymm, ymm, imm8 | xmm {k}{z}, xmm, m128/m32bcst, imm8 | ymm {k}{z}, ymm, m256/m32bcst, imm8 | zmm {k}{z}, zmm, zmm, imm8, {sae} | zmm {k}{z}, zmm, m512/m32bcst, imm8 |
|---|---|---|---|---|---|
| Skylake-SP | 4 / 0.5p01 | 10 / 0.5p01 | 11 / 0.5p01 | 4 / 0.5p05 | 11 / 0.5p05 |
| Ice Lake | 4 / 0.5p01 | 10 / 0.5p01 | 11 / 0.5p01 | 4 / 1p0 | 11 / 1p0 |
| Sapphire Rapids | 4 / 0.5p01 | 11 / 0.5p01 | 12 / 0.5p01 | 4 / 1p0 | 12 / 1p0 |
| Zen 4 | 2 / 11FP0 FP1 | 10 / 0.5FP2 FP3 | 10 / 0.5FP2 FP3 | 2 / 1FP0 FP1 | 10 / 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.
Every single works alike: 4, 8 and 16 singles 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 m32bcst, one single from memory stands for every element of the last source.
Result single i comes from single i of xmm2 and xmm3. Result singles 3 to 0: r3, unchanged (bit 2 of k1 is 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 // 32):
if k1[i]:
a = zmm2.f32[i]
b = src3.f32[i]
zmm1.f32[i] = frange(a, b, imm8)
elif zeroing:
zmm1.f32[i] = 0
# else: zmm1.f32[i] keeps its value
# imm8[1:0]: min, max, min |x|, max |x|; [3:2]: sign of a, of the result, 0, 1
# m32bcst: src3.f32[i] is the m32 for every i
# {sae}: no exception flags
# zmm1 is zeroed from bit VL upRun on AMD Zen 5 (EPYC 9645): 57 cases.
Operands
| Operand | Kind | Action |
|---|---|---|
VRANGEPS xmm {k}{z}, xmm, xmm/m128/m32bcst, imm8 VRANGEPS ymm {k}{z}, ymm, ymm/m256/m32bcst, imm8 VRANGEPS zmm {k}{z}, zmm, zmm/m512/m32bcst, imm8, {sae} | ||
xmm, ymm, zmm | explicit | write (masked) |
{k} | explicit | read (write mask) |
xmm, ymm, zmm | explicit | read |
xmm/m128/m32bcst, ymm/m256/m32bcst, zmm/m512/m32bcst | explicit | read |
imm8 | explicit | read |
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 VRANGEPS, 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.
| Intrinsic | Compiles to |
|---|---|
_mm_range_ps
__m128 _mm_range_ps(__m128 A, __m128 B, const int C) |
|
_mm_mask_range_ps
__m128 _mm_mask_range_ps(__m128 W, __mmask8 U, __m128 A, __m128 B, const int C) |
|
_mm_maskz_range_ps
__m128 _mm_maskz_range_ps(__mmask8 U, __m128 A, __m128 B, const int C) |
|
_mm256_range_ps
__m256 _mm256_range_ps(__m256 A, __m256 B, const int C) |
|
_mm256_mask_range_ps
__m256 _mm256_mask_range_ps(__m256 W, __mmask8 U, __m256 A, __m256 B, const int C) |
|
_mm256_maskz_range_ps
__m256 _mm256_maskz_range_ps(__mmask8 U, __m256 A, __m256 B, const int C) |
|
_mm512_range_ps
__m512 _mm512_range_ps(__m512 A, __m512 B, const int C) |
|
_mm512_range_round_ps
__m512 _mm512_range_round_ps(__m512 A, __m512 B, const int C, const int R) |
|
_mm512_mask_range_ps
__m512 _mm512_mask_range_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int C) |
|
_mm512_mask_range_round_ps
__m512 _mm512_mask_range_round_ps(__m512 W, __mmask16 U, __m512 A, __m512 B, const int C, const int R) |
|
_mm512_maskz_range_ps
__m512 _mm512_maskz_range_ps(__mmask16 U, __m512 A, __m512 B, const int C) |
|
_mm512_maskz_range_round_ps
__m512 _mm512_maskz_range_round_ps(__mmask16 U, __m512 A, __m512 B, const int C, const int R) |
|
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.
| ISA set | CPUID | Processors |
|---|---|---|
AVX512DQ_128 | AVX10.1 or AVX512DQ + 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_128 | Same as AVX512DQ_128 |
AVX512DQ_512 | AVX10.1 or AVX512DQ | Same as AVX512DQ_128 |
More AVX10.1 instructions
- VPTERNLOGQ
- VPTESTMB
- VPTESTMD
- VPTESTMQ
- VPTESTMW
- VPTESTNMB
- VPTESTNMD
- VPTESTNMQ
- VPTESTNMW
- VPUNPCKHBW
- VPUNPCKHDQ
- VPUNPCKHQDQ
- VPUNPCKHWD
- VPUNPCKLBW
- VPUNPCKLDQ
- VPUNPCKLQDQ
- VPUNPCKLWD
- VPXORD
- VPXORQ
- VRANGEPD
- VRANGESD
- VRANGESS
- VRCP14PD
- VRCP14PS
- VRCP14SD
- VRCP14SS
- VRCPPH
- VRCPSH
- VREDUCEPD
- VREDUCEPH
- VREDUCEPS
- VREDUCESD
- VREDUCESH
- VREDUCESS
- VRNDSCALEPD
- VRNDSCALEPH
- VRNDSCALEPS
- VRNDSCALESD
- VRNDSCALESH
- VRNDSCALESS
Sources
- Intel XED v2026.08.23 (commit
0bcb6237345c): forms, encodings, operands, flags, exception classes, attributes, ISA sets, CPUID bits and chip model. - The CPU data of x86-64.net: Zen 3 to Zen 6, from GCC’s
-marchfeature sets and AMD’s Processor Programming References, which the page of each processor cites. - 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. - LLVM 23.1.2's x86 scheduling models (commit
85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them. - Intel Advanced Vector Extensions 10.2 Architecture Specification, revision 7.0 (361050-007, April 2026)
- Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2C, page 5-665 (VRANGEPS)
- Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)
- 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.