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.
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/.
Similar to Diego's setup, Andreas Jaeger is running SPEC 2000 tests on AMD Athlon systems. For details check http://www.suse.de/~aj/SPEC/amd64/. Other AMD Athlon and PowerPC64 SPEC 2000 results are available at http://www.suse.de/~gcctest/SPEC/.
SPEC 2000 tests on Pentium 4, EM64T and PowerPC64 are available at http://people.redhat.com/dnovillo/spec2000/.
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.
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. Results can be found at http://www.suse.de/~rguenther/tramp3d/.
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.Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110, USA.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
Last modified 2006-06-21 |