Extensions
Forms
48 (12 Legacy, 36 EVEX)
Data
Intel XED v2026.08.23

SAR shifts its operand right and fills the vacated high bits with copies of the sign bit, so a negative number stays negative. It is the signed counterpart of SHR, which fills with zeros. GCC 14 and Clang 23 at -O2 compile x >> 3 on an int to sar eax, 3, and x >> 31 to a SAR by 31, which gives 0 for a non-negative x and -1 for a negative one: a mask that branch-free code ANDs or XORs with other values.

Rounding down

A right shift by k divides by 2^k rounding toward minus infinity, while C’s / and IDIV round toward zero: -7 shifted right by 1 is -4, but -7 / 2 is -3. A signed division by a power of two is therefore more than a SAR. Both compilers first add 2^k - 1 to a negative dividend, which makes the shift round up instead:

  • x / 2 becomes mov eax, edi, shr eax, 31 (the sign bit, 0 or 1), add eax, edi and sar eax;
  • x / 8 becomes lea eax, [rdi + 7], then test edi, edi and cmovns eax, edi to keep the sum only for a negative x, and sar eax, 3.

Where the dividend cannot be negative, or rounding down is what the program wants, as in x >> 3 itself, the SAR alone is the answer.

Count and flags

The count is masked to 5 bits, or 6 for a 64-bit operand, as for SHL, so a byte shifted by 8 to 31 becomes 0 or -1 depending on its sign. A shift by 1 always clears OF, since the sign cannot change; the note under the flags table says where XED differs. A count of 0 changes no flag, which is why Intel’s optimization manual names shifts as the usual cause of partial flag stalls and recommends a TEST of the result before a SETcc or Jcc that depends on it (Section 3.5.2.5).

SARX from BMI2 takes the count from any register, writes a separate destination and leaves the flags alone; with -march=x86-64-v3, both compilers use it for x >> n. APX adds forms with a new destination and forms that leave the flags unchanged (NF).

In the optimization guide

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

Out of order

  • Partial register and flag writes: A shift or rotate by CL leaves the flags alone when the count is zero, which is known only when it runs, so it depends on the old flags too.

Forms

Every encoding of SAR that Intel XED knows, one row per XED instruction form (iform). How to read the notation.
InstructionEncodingRequires
SAR m8, imm8 SAR_MEMb_IMMbC0 /7 ibBase instruction set
SAR r8, imm8 SAR_GPR8_IMMbC0 /7 ibBase instruction set
SAR m16/32/64, imm8 SAR_MEMv_IMMbC1 /7 ibBase instruction set
SAR r16/32/64, imm8 SAR_GPRv_IMMbC1 /7 ibBase instruction set
SAR m8, 1 SAR_MEMb_ONED0 /7Base instruction set
SAR r8, 1 SAR_GPR8_ONED0 /7Base instruction set
SAR m16/32/64, 1 SAR_MEMv_ONED1 /7Base instruction set
SAR r16/32/64, 1 SAR_GPRv_ONED1 /7Base instruction set
SAR m8, CL SAR_MEMb_CLD2 /7Base instruction set
SAR r8, CL SAR_GPR8_CLD2 /7Base instruction set
SAR m16/32/64, CL SAR_MEMv_CLD3 /7Base instruction set
SAR r16/32/64, CL SAR_GPRv_CLD3 /7Base instruction set
SAR r8, imm8 SAR_GPR8i8_IMM8_APXEVEX.LLZ.NP.MAP4.WIG C0 /7 ibAPX_F
SAR m8, imm8 SAR_MEMi8_IMM8_APXEVEX.LLZ.NP.MAP4.WIG C0 /7 ibAPX_F
SAR r8, imm8 NF SAR_GPR8i8_IMM8_APX_N3EVEX.LLZ.NP.MAP4.WIG C0 /7 ib NF=1APX_F + APX_NCI_NDD_NF
SAR m8, imm8 NF SAR_MEMi8_IMM8_APX_N3EVEX.LLZ.NP.MAP4.WIG C0 /7 ib NF=1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, r16/32/64, imm8 NDD NF optional SAR_GPRv_GPRv_IMM8_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE C1 /7 ib ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, m16/32/64, imm8 NDD NF optional SAR_GPRv_MEMv_IMM8_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE C1 /7 ib ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r8, 1 SAR_GPR8i8_ONE_APXEVEX.LLZ.NP.MAP4.WIG D0 /7APX_F
SAR m8, 1 SAR_MEMi8_ONE_APXEVEX.LLZ.NP.MAP4.WIG D0 /7APX_F
SAR r8, 1 NF SAR_GPR8i8_ONE_APX_N3EVEX.LLZ.NP.MAP4.WIG D0 /7 NF=1APX_F + APX_NCI_NDD_NF
SAR m8, 1 NF SAR_MEMi8_ONE_APX_N3EVEX.LLZ.NP.MAP4.WIG D0 /7 NF=1APX_F + APX_NCI_NDD_NF
SAR r8, r8, 1 NDD NF optional SAR_GPR8i8_GPR8i8_ONE_APX_N3EVEX.LLZ.NP.MAP4.WIG D0 /7 ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r8, m8, 1 NDD NF optional SAR_GPR8i8_MEMi8_ONE_APX_N3EVEX.LLZ.NP.MAP4.WIG D0 /7 ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, 1 SAR_GPRv_ONE_APXEVEX.LLZ.NP.MAP4.SCALABLE D1 /7APX_F
SAR m16/32/64, 1 SAR_MEMv_ONE_APXEVEX.LLZ.NP.MAP4.SCALABLE D1 /7APX_F
SAR r16/32/64, 1 NF SAR_GPRv_ONE_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE D1 /7 NF=1APX_F + APX_NCI_NDD_NF
SAR m16/32/64, 1 NF SAR_MEMv_ONE_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE D1 /7 NF=1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, r16/32/64, 1 NDD NF optional SAR_GPRv_GPRv_ONE_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE D1 /7 ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, m16/32/64, 1 NDD NF optional SAR_GPRv_MEMv_ONE_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE D1 /7 ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r8, CL SAR_GPR8i8_CL_APXEVEX.LLZ.NP.MAP4.WIG D2 /7APX_F
SAR m8, CL SAR_MEMi8_CL_APXEVEX.LLZ.NP.MAP4.WIG D2 /7APX_F
SAR r8, CL NF SAR_GPR8i8_CL_APX_N3EVEX.LLZ.NP.MAP4.WIG D2 /7 NF=1APX_F + APX_NCI_NDD_NF
SAR m8, CL NF SAR_MEMi8_CL_APX_N3EVEX.LLZ.NP.MAP4.WIG D2 /7 NF=1APX_F + APX_NCI_NDD_NF
SAR r8, r8, CL NDD NF optional SAR_GPR8i8_GPR8i8_CL_APX_N3EVEX.LLZ.NP.MAP4.WIG D2 /7 ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r8, m8, CL NDD NF optional SAR_GPR8i8_MEMi8_CL_APX_N3EVEX.LLZ.NP.MAP4.WIG D2 /7 ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, CL SAR_GPRv_CL_APXEVEX.LLZ.NP.MAP4.SCALABLE D3 /7APX_F
SAR m16/32/64, CL SAR_MEMv_CL_APXEVEX.LLZ.NP.MAP4.SCALABLE D3 /7APX_F
SAR r16/32/64, CL NF SAR_GPRv_CL_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE D3 /7 NF=1APX_F + APX_NCI_NDD_NF
SAR m16/32/64, CL NF SAR_MEMv_CL_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE D3 /7 NF=1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, r16/32/64, CL NDD NF optional SAR_GPRv_GPRv_CL_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE D3 /7 ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, m16/32/64, CL NDD NF optional SAR_GPRv_MEMv_CL_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE D3 /7 ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r8, r8, imm8 NDD NF optional SAR_GPR8i8_GPR8i8_IMM8_APX_N3EVEX.LLZ.NP.MAP4.WIG C0 /7 ib ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r8, m8, imm8 NDD NF optional SAR_GPR8i8_MEMi8_IMM8_APX_N3EVEX.LLZ.NP.MAP4.WIG C0 /7 ib ND=1 NF=0/1APX_F + APX_NCI_NDD_NF
SAR r16/32/64, imm8 SAR_GPRv_IMM8_APXEVEX.LLZ.NP.MAP4.SCALABLE C1 /7 ibAPX_F
SAR m16/32/64, imm8 SAR_MEMv_IMM8_APXEVEX.LLZ.NP.MAP4.SCALABLE C1 /7 ibAPX_F
SAR r16/32/64, imm8 NF SAR_GPRv_IMM8_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE C1 /7 ib NF=1APX_F + APX_NCI_NDD_NF
SAR m16/32/64, imm8 NF SAR_MEMv_IMM8_APX_N3EVEX.LLZ.NP.MAP4.SCALABLE C1 /7 ib NF=1APX_F + APX_NCI_NDD_NF

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.
Modelm8, imm8
m8, 1
r8, imm8
r16, imm8
r32, imm8
r64, imm8
r8, 1
r16, 1
r32, 1
r64, 1
m16, imm8
m32, imm8
m64, imm8
m16, 1
m32, 1
m64, 1
m8, CLr8, CL
r16, CL
r32, CL
r64, CL
m16, CL
m32, CL
m64, CL
Sandy Bridge7 / 1p051 / 0.5p057 / 1p059 / 1.5p053 / 1.5p059 / 1.5p05
Haswell7 / 1p061 / 0.5p067 / 1p069 / 1p01563 / 1.5p069 / 1p0156
Broadwell6 / 1p061 / 0.5p066 / 1p068 / 1p01563 / 1.5p068 / 1p0156
Skylake, Skylake-SP6 / 1p061 / 0.5p066 / 1p068 / 1.5p063 / 1.5p068 / 1.5p06
Ice Lake6 / 0.5p061 / 0.5p066 / 0.5p068 / 1.5p063 / 1.5p068 / 1.5p06
Alder Lake, Sapphire Rapids13 / 0.5p061 / 0.5p0612 / 0.5p0613 / 1p062 / 1p0612 / 1p06
Lunar Lake13 / 0.5p0241 / 0.33p1355 / 1.67p13513 / 0.67p0242 / 0.67p02412 / 0.67p024
Bonnell1 / 1p01 / 1p01 / 1p01 / 1p01 / 1p01 / 1p0
Silvermont4 / 2IEC0 MEC1 / 1IEC04 / 2IEC0 MEC4 / 2IEC0 MEC1 / 1IEC04 / 2IEC0 MEC
Piledriver5 / 2EX0 EX11 / 1EX0 EX15 / 2EX0 EX15 / 2EX0 EX11 / 0.5EX0 EX15 / 2EX0 EX1
Zen5 / 0.5ALU0 ALU1 ALU2 ALU31 / 0.25ALU0 ALU1 ALU2 ALU35 / 0.5ALU0 ALU1 ALU2 ALU35 / 1ALU0 ALU1 ALU2 ALU31 / 0.25ALU0 ALU1 ALU2 ALU35 / 1ALU0 ALU1 ALU2 ALU3
Zen 25 / 0.33ALU0 ALU1 ALU2 ALU31 / 0.25ALU0 ALU1 ALU2 ALU35 / 0.33ALU0 ALU1 ALU2 ALU35 / 0.67ALU0 ALU1 ALU2 ALU31 / 0.25ALU0 ALU1 ALU2 ALU35 / 0.67ALU0 ALU1 ALU2 ALU3
Zen 3, Zen 45 / 0.67ALU1 ALU21 / 0.5ALU1 ALU25 / 0.67ALU1 ALU25 / 0.67ALU1 ALU21 / 0.5ALU1 ALU25 / 0.67ALU1 ALU2
Jaguar4 / 1ALU0 ALU11 / 0.5ALU0 ALU14 / 1ALU0 ALU14 / 1ALU0 ALU11 / 0.5ALU0 ALU14 / 1ALU0 ALU1

Operation

What the forms do, in pseudocode that our tests run against results recorded on real processors. How to read.

All forms but the NDD forms
s = signed(dest)                 # the value as a signed number
n = count & (0x3F if OSIZE == 64 else 0x1F)   # the count is masked
r = low(s >> n)                  # copies of the sign bit come in
if n != 0 and not nf:            # a count of 0 changes no flag; NF=1
                                 # (APX) none at all
    cf = s >> (n - 1) & 1        # the last bit shifted out: the sign
                                 # bit once n > OSIZE
    of = 0 if n == 1 else UNDEFINED   # the sign never changes
    sf = msb(r)
    zf = r == 0
    pf = parity(r)
    af = UNDEFINED
dest.write(r)                    # even for a count of 0, a 32-bit register
                                 # gets bits 63:32 cleared

Run on AMD Zen 5 (EPYC 9645): 225 cases. The APX forms were not run: none of these processors has APX.

NDD forms
s = signed(src)                  # the value as a signed number
n = count & (0x3F if OSIZE == 64 else 0x1F)   # the count is masked
r = low(s >> n)                  # copies of the sign bit come in
if n != 0 and not nf:            # a count of 0 changes no flag; NF=1
                                 # none at all
    cf = s >> (n - 1) & 1        # the last bit shifted out: the sign
                                 # bit once n > OSIZE
    of = 0 if n == 1 else UNDEFINED   # the sign never changes
    sf = msb(r)
    zf = r == 0
    pf = parity(r)
    af = UNDEFINED
dest.write(r)                    # the new destination: bits 63:OSIZE
                                 # cleared, even for 8 and 16 bits

Not run on a processor: none of these processors has APX.

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
SAR r/m8, imm8 SAR r/m16/32/64, imm8
r/m8/16/32/64explicitread, write
imm8explicitread
RFLAGSimplicitwrite
SAR r/m8, 1 SAR r/m16/32/64, 1
r/m8/16/32/64explicitread, write
1explicitread
RFLAGSimplicitwrite
SAR r/m8, CL SAR r/m16/32/64, CL
r/m8/16/32/64explicitread, write
CLexplicitread
RFLAGSimplicitconditional write
SAR r/m8, imm8 NF SAR r/m16/32/64, imm8 NF
r/m8/16/32/64explicitread, write
imm8explicitread
SAR r8, r/m8, imm8 NDD NF optional SAR r16/32/64, r/m16/32/64, imm8 NDD NF optional
r8/16/32/64explicitwrite
r/m8/16/32/64explicitread
imm8explicitread
RFLAGSimplicitwrite (NF=0)
SAR r/m8, 1 NF SAR r/m16/32/64, 1 NF
r/m8/16/32/64explicitread, write
1explicitread
SAR r8, r/m8, 1 NDD NF optional SAR r16/32/64, r/m16/32/64, 1 NDD NF optional
r8/16/32/64explicitwrite
r/m8/16/32/64explicitread
1explicitread
RFLAGSimplicitwrite (NF=0)
SAR r/m8, CL NF SAR r/m16/32/64, CL NF
r/m8/16/32/64explicitread, write
CLexplicitread
SAR r8, r/m8, CL NDD NF optional SAR r16/32/64, r/m16/32/64, CL NDD NF optional
r8/16/32/64explicitwrite
r/m8/16/32/64explicitread
CLexplicitread
RFLAGSimplicitconditional write (NF=0)

Flags

M modified, U undefined; blank: not affected. With NF=1, the forms with optional NF leave the flags unchanged. How to read.
WhenOFSFZFAFPFCF
SAR r/m8, imm8 SAR r/m16/32/64, imm8
count 1MMMUMM
count 2 or moreUMMUMM
SAR r/m8, 1 SAR r/m16/32/64, 1
MMMUMM
SAR r/m8, CL SAR r/m16/32/64, CL
in some casesUMMUMM
NF forms
Not affected
SAR r8, r/m8, imm8 NDD NF optional SAR r16/32/64, r/m16/32/64, imm8 NDD NF optional
NF=0, count 1MMMUMM
NF=0, count 2 or moreUMMUMM
SAR r8, r/m8, 1 NDD NF optional SAR r16/32/64, r/m16/32/64, 1 NDD NF optional
NF=0MMMUMM
SAR r8, r/m8, CL NDD NF optional SAR r16/32/64, r/m16/32/64, CL NDD NF optional
NF=0, in some casesUMMUMM

Exceptions

The exception class is XED's name for the set of exception conditions that a form follows. How to read.

Legacy forms
none in XED
EVEX forms
APX-EVEX-INT

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
I186

No CPUID bit: part of the base instruction set.

Every x86-64 processor in XED’s model and Zen 3 to Zen 6
I86

No CPUID bit: part of the base instruction set.

Every x86-64 processor in XED’s model and Zen 3 to Zen 6
APX_F

APX_F
CPUID.(EAX=07H,ECX=1):EDX[21] APX_F

Nova Lake, Diamond Rapids
APX_F_N3

APX_F + APX_NCI_NDD_NF
CPUID.(EAX=07H,ECX=1):EDX[21] APX_F
CPUID.(EAX=29H,ECX=0):EBX[0] APX_NCI_NDD_NF

Same as APX_F

More General-purpose instructions

All 109 General-purpose instructions

More APX instructions

All 88 APX 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. LLVM 23.1.2's x86 scheduling models (commit 85ac56026243): the latency, reciprocal throughput and ports of each form, as llvm-mca reports them.
  4. Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 2 (325383-093, September 2026): Volume 2B, page 4-603 (SAL/SAR/SHL/SHR)
  5. Intel Advanced Performance Extensions (Intel APX) Architecture Specification, revision 9.0 (355828-009, August 2026)
  6. AMD64 Architecture Programmer's Manual, Volume 3: General-Purpose and System Instructions (24594, rev. 3.39, October 2026)
  7. Intel 64 and IA-32 Architectures Optimization Reference Manual, Volume 1 (248966-051, October 2026)

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.