Instruction
SHRX
Shifts the source right logically by a count in a register into a separate destination without touching the flags.
SHRX shifts its source right logically, zeros coming in at the top, by a
count from any register, and writes a third register without touching
the flags. It is SHR with the count anywhere but in CL and
with a separate destination; SARX, whose page explains
why such shifts leave the flags alone, is the arithmetic sibling and
SHLX the left one. In Intel syntax the count comes last:
shrx eax, edi, esi is EDI » ESI.
Unsigned shifts in C
With -march=x86-64-v3, GCC 14 and Clang 23 at -O2 compile x >> n on an
unsigned or uint64_t to a single SHRX, and a bit field read at a
variable position, (x >> s) & ((1ULL << k) - 1), to SHRX followed by
BZHI. A load can be the source: Clang folds *p >> n
into shrx rax, qword ptr [rdi], rsi, while GCC loads with a MOV first.
A shift by a constant stays shr rax, 7, as SHRX has no immediate form.
A count of the full width
Only the low 5 bits of the count are used, 6 for a 64-bit operand. On
Zen 5, a count of 32 left a 32-bit value unchanged and a count of 33
shifted it by 1; a count of 64 left a 64-bit value unchanged. C makes a
shift by the width undefined for this reason, and code that needs
x >> 32 to give 0 must ask for it: GCC and Clang compile
n < 32 ? x >> n : 0 to SHRX, a CMP of the count with 32 and a CMOV
that picks 0.
The masking can also help. Clang compiles x >> (32 - s) to neg sil
and SHRX, since 32 - s and -s agree in their low 5 bits; GCC computes
the subtraction.
Forms and speed
The destination is written whole: a 32-bit form clears bits 63:32. APX adds EVEX forms that reach its new registers. AMD’s Zen 5 instruction table lists SHRX, like SHR, as one macro-op with a latency of one cycle, three per cycle. SHRX belongs to BMI2, part of x86-64-v3.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
SHRX r32, m32, r32
SHRX_GPR32d_MEMd_GPR32d | VEX.LZ.F2.0F38.W0 F7 /r | BMI2 |
SHRX r32, r32, r32
SHRX_GPR32d_GPR32d_GPR32d | VEX.LZ.F2.0F38.W0 F7 /r | BMI2 |
SHRX r64, m64, r64 64-bit mode only
SHRX_GPR64q_MEMq_GPR64q | VEX.LZ.F2.0F38.W1 F7 /r | BMI2 |
SHRX r64, r64, r64 64-bit mode only
SHRX_GPR64q_GPR64q_GPR64q | VEX.LZ.F2.0F38.W1 F7 /r | BMI2 |
SHRX r32, r32, r32
SHRX_GPR32i32_GPR32i32_GPR32i32_APX | EVEX.LLZ.F2.0F38.W0 F7 /r | APX_F + BMI2 |
SHRX r32, m32, r32
SHRX_GPR32i32_MEMi32_GPR32i32_APX | EVEX.LLZ.F2.0F38.W0 F7 /r | APX_F + BMI2 |
SHRX r64, r64, r64
SHRX_GPR64i64_GPR64i64_GPR64i64_APX | EVEX.LLZ.F2.0F38.W1 F7 /r | APX_F + BMI2 |
SHRX r64, m64, r64
SHRX_GPR64i64_MEMi64_GPR64i64_APX | EVEX.LLZ.F2.0F38.W1 F7 /r | APX_F + BMI2 |
Latency and throughput
| Model | r32, m32, r32r64, m64, r64 | r32, r32, r32r64, r64, r64 |
|---|---|---|
| Haswell, Broadwell, Skylake, Skylake-SP, Ice Lake | 6 / 0.5p06 | 1 / 0.5p06 |
| Alder Lake, Sapphire Rapids | 8 / 0.5p06 | 3 / 0.5p06 |
| Lunar Lake | 8 / 0.33p024 | 3 / 0.33p024 |
| Zen | 5 / 0.5ALU0 ALU1 ALU2 ALU3 | 1 / 0.25ALU0 ALU1 ALU2 ALU3 |
| Zen 2 | 5 / 0.33ALU0 ALU1 ALU2 ALU3 | 1 / 0.25ALU0 ALU1 ALU2 ALU3 |
| Zen 3, Zen 4 | 5 / 0.5ALU1 ALU2 | 1 / 0.5ALU1 ALU2 |
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
n = count & (0x3F if OSIZE == 64 else 0x1F) # the count is masked
dest.write(src >> n) # zeros come in from the top; no flag
# changes, whatever the count
Run on AMD Zen 5 (EPYC 9645): 45 cases. The APX forms were not run: none of these processors has APX.
Operands
| Operand | Kind | Action |
|---|---|---|
SHRX r32, r/m32, r32 SHRX r64, r/m64, r64 64-bit mode only | ||
r32/64 | explicit | write |
r/m32/64 | explicit | read |
r32/64 | 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.
- VEX forms
- none in XED
- EVEX forms
APX-EVEX-BMI
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 |
|---|---|---|
BMI2 | BMI2 | 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, Sierra Forest, Clearwater Forest, Knights Landing, Knights Mill, Zen, Zen+, Zen 2, Zen 3, Zen 4, Zen 5, Zen 6 |
APX_F_BMI2 | APX_F + BMI2 | Nova Lake, Diamond Rapids |
More BMI2 instructions
More APX instructions
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. - 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 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-609 (SARX/
SHLX/ SHRX) - Intel Advanced Performance Extensions (Intel APX) Architecture Specification, revision 9.0 (355828-009, August 2026)
- AMD64 Architecture Programmer's Manual, Volume 3: General-Purpose and System Instructions (24594, rev. 3.39, 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 timings come from LLVM's scheduling models, part of the LLVM Project, licensed under the Apache License 2.0 with LLVM Exceptions. The text is our own.