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 95

Diego Novillo has set up a Pentium III system that runs daily SPEC 95 tests. The results can be seen at http://people.redhat.com/dnovillo/spec95/.

SPEC 2000

Similar to Diego's setup, other AMD Athlon and PowerPC64 SPEC 2000 results are available at http://www.suse.de/~gcctest/.

SPEC 2000 tests on Pentium 4, EM64T and PowerPC64 are available at http://people.redhat.com/dnovillo/spec2000/.

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

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 http://annwm.lbl.gov/bench/.

Richard Günther 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 http://www.suse.de/~gcctest/c++bench/.

Tobias Burnus also runs the Polyhedron benchmark with mainline GCC. Results can be found at http://www.physik.fu-berlin.de/~tburnus/gcc-trunk/benchmark/.

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 http://www.suse.de/~gcctest/memory/

Openbench

Openbench is an open source benchmarking suite similar to SPEC.

Please send FSF & GNU inquiries & questions to gnu@gnu.org. There are also other ways to contact the FSF.

These pages are maintained by the GCC team.

For questions related to the use of GCC, please consult these web pages and the GCC manuals. If that fails, the gcc-help@gcc.gnu.org mailing list might help.
Please send comments on these web pages and the development of GCC to our developer mailing list at gcc@gnu.org or gcc@gcc.gnu.org. All of our lists have public archives.

Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.

Last modified 2007-02-19