SPEC CPU result comparison

15th October 2026 - Normalized report

SPEC2026 INTrate: LTO -O2 x86-64-v3 - LLVM and GCC

-O2 -flto -march=x86-64-v3

Please note that the same "optimization levels" mean different things to different compilers. For example, LLVM and LLVM-based compiler tend to be much more aggressive at -O2, often with the corresponding consequences to size of the generated binaries and compilation time. GCC is sometimes more aggressive at -O3. LLVM is also often by default less strict when it comes to standard compliance by default and performs optimizations GCC would only do with a special compilation option or at -Ofast. Keep this is mind when comparing different compilers.

AMD EPYC 8635P (zen5 based Sorano)

Run-times

Benchmark LLVM GCC
706.stockfish_r 100.00% 89.78%
707.ntest_r 100.00% 105.43%
708.sqlite_r 100.00% 96.36%
710.omnetpp_r 100.00% 93.60%
714.cpython_r 100.00% 96.48%
721.gcc_r 100.00% 99.36%
723.llvm_r 100.00% 108.09%
727.cppcheck_r 100.00% 102.31%
729.abc_r 100.00% 98.21%
734.vpr_r 100.00% 98.77%
735.gem5_r 100.00% 96.71%
750.sealcrypto_r 100.00% 100.00%
753.ns3_r 100.00% 105.87%
777.zstd_r 100.00% 102.90%
LLVM clang version 23.1.3 (/labs/mjambor/git/llvm 0d261d1ca552c95a8f007e061c787ac7132fbcbc), flang version 23.1.3 (/labs/mjambor/git/llvm 0d261d1ca552c95a8f007e061c787ac7132fbcbc)
GCC GCC 17.0.0 20261015 (experimental) (revision 84348add236100e5f69a3e9ec4f7b1038bf2b83d)
Naturally, the smaller the run-times, the better.

Non-debug executable sizes

Benchmark LLVM GCC
706.stockfish_r 100.00% 99.96%
707.ntest_r 100.00% 98.04%
708.sqlite_r 100.00% 83.10%
710.omnetpp_r 100.00% 99.06%
714.cpython_r 100.00% 86.79%
721.gcc_r 100.00% 90.35%
723.llvm_r 100.00% 87.80%
727.cppcheck_r 100.00% 88.18%
729.abc_r 100.00% 86.96%
734.vpr_r 100.00% 89.55%
735.gem5_r 100.00% 95.53%
750.sealcrypto_r 100.00% 82.24%
753.ns3_r 100.00% 81.21%
777.zstd_r 100.00% 94.72%
Smaller binary sizes are always better.