Instruction
LES
Loads a far pointer from memory into a register and ES; not in 64-bit mode, where its opcode C4 starts a VEX prefix.
- Extensions
- Forms
- 1 (1 Legacy)
- Data
- Intel XED v2026.08.23
LES loads a far pointer from memory: the offset into a general-purpose register and the 16-bit selector after it into ES, m16:32 at the 32-bit operand size and m16:16 at the 16-bit one. Everything else is as for LDS: the descriptor check of a MOV to ES in protected mode, a null selector accepted until ES is used, and a plain load in real mode. ES is the segment of the destination of the string instructions, such as MOVS and STOS, so LES and LDS together set up a copy between two segments. LFS shows the same load on Zen 5 for FS, which 64-bit mode kept.
C4 became VEX
C4 with a ModRM byte of mod = 11b was never a valid LES, and the three-byte VEX prefix uses those bytes in 32-bit code. Intel’s manual says that the bits after C4 that hold VEX.R and VEX.X, inverted, must both be 1 there, otherwise the instruction is LES. Both select registers 8 to 15, which 32-bit code does not have. In 64-bit mode C4 always starts a VEX prefix, and LES does not exist.
Not in 64-bit mode
The fixture has no case for LES: the probe runs in 64-bit mode, where C4
starts a VEX instruction, and lists the form as not run. GNU as 2.44 and
Clang 23 refuse les in 64-bit code. AMD’s Zen 5 guide lists LES as
microcoded, without a latency.
Forms
| Instruction | Encoding | Requires |
|---|---|---|
LES r16/32, m16:16/32 not in 64-bit mode
LES_GPRz_MEMp | C4 /r | Base instruction set |
Operation
What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.
v = src.read() # m16:16 or m16:32
load_segment(es, v >> OSIZE) # checks the descriptor it names
dest.write(v) # the offset: the low OSIZE bits
Not run on a processor: LES does not exist in 64-bit mode, where the probe runs: C4 starts a VEX prefix there.
Operands
| Operand | Kind | Action |
|---|---|---|
LES r16/32, m16:16/32 not in 64-bit mode | ||
r16/32 | explicit | write |
m16:16/32 | explicit | read |
ES | implicit | write |
Flags
None: XED records no flag that the forms test or change.
Attributes
What else XED records about the forms. How to read.
- All forms
- may abort a TSX transaction
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. - Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2A, page 3-540 (LDS/
LES/ LFS/ LGS/ LSS) - 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 text is our own.