Instruction
LOOPE
Decrements RCX, ECX or CX without changing the flags and jumps to a short relative target if the count is not zero and ZF is set.
- Extensions
- Mnemonics
- LOOPE, LOOPZ
- Forms
- 1 (1 Legacy)
- Data
- Intel XED v2026.08.23
LOOPE (also LOOPZ, E1 cb) works like LOOP: it subtracts 1 from RCX, ECX with a 67 prefix, without touching the flags, and jumps to a short relative target while the count is not zero, but only if ZF is also 1. It reads ZF as an earlier instruction left it, typically a CMP in the loop body, so the loop runs while the elements compare equal and stops at the first difference or when the count runs out. LOOPNE stops at the first match instead. LOOP’s page covers the counter’s size, a count of 0 and why compilers avoid the family.
Which condition ended it
Since LOOPE leaves the flags alone, ZF after the loop tells the two
exits apart: 0 means the last compare found a difference, 1 means every
element compared equal and the count ran out. This is the counted loop
that repe cmpsb performs in one instruction, as the
CMPS page describes, but with any compare in the body.
On Zen 5
- With RCX = 2 and ZF = 1 it jumped and left RCX = 1; with ZF = 0 it fell through, RCX decremented all the same.
- With RCX = 0 and ZF = 1 it wrapped RCX to 2^64 - 1 and jumped.
- RCX = 2^32 became 2^32 - 1: the whole register counts. With a 67 prefix, ECX = 0 in a register whose upper half was nonzero became FFFFFFFFh with bits 63:32 cleared.
Neither GCC 14 nor Clang 23 emits it in our builds, at -O2 or at -Os. AMD’s Zen 5 guide lists LOOPE, like LOOP, as microcoded, where a CMP and a JE fuse into one macro-op.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
LOOPE rel8
LOOPE_RELBRb | E1 cb | Base instruction set |
Latency and throughput
| Model | rel8 |
|---|---|
| Sandy Bridge | 4 / 4p015 |
| Haswell, Broadwell, Skylake, Skylake-SP, Ice Lake | 11 / 2.75p0156 |
| Alder Lake, Sapphire Rapids | 3 / 3p0 p1 p5 p6 p11 |
| Lunar Lake | 3 / 2p012345 |
| Bonnell | 8 / 4p01 |
| Silvermont | 1 / 1IEC1 |
| Piledriver | 1 / 1Branch EX1 |
| Zen, Zen 2 | 1 / 0.5ALU0 ALU3 |
| Zen 3, Zen 4 | 1 / 0.5ALU0 BRU1 |
| Jaguar | 1 / 0.5ALU0 ALU1 |
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
w = OSIZE # as LOOP's
if OSIZE == 16:
if INTEL:
w = 64 # ignored: SDM
c = low(aCX - 1, ASIZE) # RCX; ECX with a 67 prefix
aCX = c
if c != 0 and zf == 1: # ZF from before, which LOOPE leaves
t = low(rip + signed(rel), w)
if not canonical(t):
fault(GP, 0)
rip = tRun on AMD Zen 5 (EPYC 9645): 16 cases. Its branches for Intel's processors were not run: no Intel processor ran these forms.
Operands
| Operand | Kind | Action |
|---|---|---|
LOOPE rel8 | ||
rel8 | explicit | read |
rCX | implicit | read, write |
rIP | implicit | read, write |
RFLAGS | implicit | read |
Flags
| ZF |
|---|
| All forms |
| T |
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 |
|---|---|---|
I86 | No CPUID bit: part of the base instruction set. | Every x86-64 processor in XED’s model and Zen 3 to Zen 6 |
More General-purpose 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 2A, page 3-570 (LOOP/
LOOPcc) - 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.