Spec 2000 : cross compilation & results
The benchmarks bellow are statically compiled using the Spec2000 compilation process. The configuration files used to compile the suite are the following: i586.cfg and ppc.cfg and running:
runspec -a build -c XXX.cfg
The i586 version is built using gcc, g++ and gfortran 4.1. The powerpc version is built with a gcc and g++ cross compilers version 3.4.5 with a glibc 2.3.2. The produced benchmarks are statically linked.
The following table provide the runnning time of the benchmarks in the suite for running the benchmark natively (i586), in a functional simulator (ppcemu) and in a cycle-level simulator (ppc-score).
Two diffrent data-set are provided: Test (the regular test data-set of the spec 2000) and tiny: a very small dataset built to keep small cycle-level simualtion time.
| test runtime (hh:mm:ss.ss) | |||||
|---|---|---|---|---|---|
| Spec | tar.gz | i586 | ppcemu 750 | ppcemu 405 | ppc-score |
| 164.gzip | 164.gzip.tar.gz | 00:00:00.50 | 00:02:54.00 | 00:02:52.00 | |
| 175.vpr | 175.vpr.tar.gz | 00:00:10.00 | 00:06:56.00 | 04:52:50.00 | |
| 176.gcc | X | X | X | ||
| 181.mcf | 181.mcf.tar.gz | 00:00:00.20 | 00:00:21.00 | 00:00:22.00 | |
| 186.crafty | 186.crafty.tar.gz | 00:00:03.00 | 00:17:50.00 | 00:17:45.00 | |
| 197.parser | 197.parser.tar.gz | 00:00:01.42 | 01:12:07.00 | 01:06:55.00 | |
| 252.eon | X | X | X | ||
| 253.perlbmk | X | X | X | ||
| 254.gap | 254.gap.tar.gz | 00:00:00.44 | SC! | SC! | |
| 255.vortex | 255.vortex.tar.gz | 00:00:05.00 | 00:26:51.00 | 00:27:19.00 | |
| 256.bzip2 | 256.bzip2.tar.gz | 00:02:19.00 | 00:08:50.00 | 00:09:09.00 | |
| 300.twolf | 300.twolf.tar.gz | 00:00:00:20 | 00:00:38.00 | 00:02:17.00 | |
Legend
X: Some issues to compile this benchmark with a recent version of gcc, even on the native host.SC!: Gap is using the unimplementedstatsyscall.
tar.gz file
In each tar.gz file there is two binaries corresponding to the statically compiled benchmarks, and the file corresponding to the test data set. In each tar.gz, there is a run file describing what should be the command line to run the spec.
