Benchmarking GCC

For evaluation of the code generated by GCC a number of benchmarks are available. Some people run these benchmarks on a regular basis and therefore allow to monitor how GCC's optimizations evolve over time and whether optimizations really make a difference on the tested benchmarks.

SPEC 2000

AMD Athlon and PowerPC64 SPEC 2000 results are available at

SPEC 2000 results on Intel Core2 are available at The scripts used are based on original scripts by Diego Novillo.

SPEC 2000 results on Intel Core2, Intel P4 and PowerPC 64 are available at

SPEC 2006

SPEC 2006 results on Intel Core2 are available at the same place as SPEC2000 ones:

Code Size Benchmarks

Statistics about GCC code size for several targets are available from the GCC Code-Size Benchmark Environment (CSiBE), along with the testbed and measurement scripts.

Related benchmarks and scripts

Charles Leggett runs several benchmarks (Bench++, Haney, Stepanov, OOPACK) comparing various versions of GCC and KAI KCC with several optimization levels. Results can be found at

Richard Biener runs TraMP3d-v4 tracking mainline GCC compile and runtime performance and its memory usage. Various other C++ benchmarks and Polyhedron are run also, results can be found at

Tobias Burnus also runs the Polyhedron benchmark with mainline GCC. Results can be found at

Joost VandeVondele runs a CP2K benchmark with mainline GCC. Results can be found at

A memory tester (maintained by Jan Hubicka) is periodically checking GCC memory usage. The reports are sent to the gcc-regressions mailing list when some noticeable change is detected. Dumps from the latest run and summaries are available at

Diego Novillo compiled a collection of relevant scripts at


Openbench is a free benchmarking suite similar to SPEC.