Developer knowledge network · moderated exchange

UnreliableCode-Community

Community für Entwicklerforschung, Reverse Engineering und Codierung

Knowledge indexLive
4Categories
919Threads
2.8KBeiträge
Analysis

Comparing Compiler Optimization Passes: -O2 vs -O3 vs -Os vs -Ofast in GCC and Clang [StackOverflow Architecture Guide]

llvm_compiler_dev
LLVM & Clang Hacker
MEMBER
Vertreter: 139
Beitrittsdatum: Jul 2018
Beiträge: 21
Danke: 15
Vor 1 Monaten · Jul 15, 2026 7:13 AM
#1

What compiler optimization flags actually enable under the hood:

  • -O2: Enables standard optimizations (instruction scheduling, register allocation, inlining, common subexpression elimination).
  • -O3: Adds aggressive loop unrolling, SIMD auto-vectorization, and function cloning (can increase binary code size).
  • -Os / -Oz: Prioritizes code compactness, disabling loop unrolling to maximize CPU L1 Instruction Cache hits.
  • -Ofast: Enables -O3 plus -ffast-math (breaks IEEE 754 floating point standard compliance and NaN/Infinity guarantees!).
profiler_pat
Performance Hunter
MEMBER
Vertreter: 146
Beitrittsdatum: Aug 2019
Beiträge: 33
Danke: 31
Vor 1 Monaten · Jul 15, 2026 12:50 PM
#2

Warning: Never use -Ofast in financial, cryptographic, or physics simulation software because -ffast-math assumes floats are associative and ignores NaN checks.

assembly_micro_dev
x86_64 Micro-arch
MEMBER
Vertreter: 186
Beitrittsdatum: Oct 2021
Beiträge: 10
Danke: 27
Vor 1 Monaten · Jul 15, 2026 11:39 PM
#3

In many instruction-cache bound servers, -Os actually outperforms -O3 due to fewer L1i cache misses!