Originally posted by: Eug
go to Aceshardware to see the actual SPEC results. Apple used their own compiler for the tests on the P4/Xeon platforms.
Why would Apple be making compilers for Linux on x86? That makes no sense whatsoever. As EdipisReks says, the compiler used for the PC is a very popular one. Gnu C Compiler (GCC) 3.3, on Linux. It's so popular because it's widely available and free, and apparently produces reasonably good code.
It's widely used under Unix when "good enough" performance is required. It is not as widely used for HPC applications.
The real culprit for the SPECfp discrepancy is not GCC...10 of the 14 SPECfp tests are written in Fortan, not C. For these, NAGware's Fortran compiler was used, and the results were not pretty (these are the geometric means calculated from the official SPEC results and Veritest's disclosure):
C programs (177.mesa, 179.art, 183.equake, 188.ammp):
3 GHz P4:
* ICC: 1086
* GCC: 788
2 GHz G5 (GCC): 778
Fortran programs (168.wupwise, 171.swim, 172.mgrid, 173.applu, 178.galgel, 187.facerec, 189.lucas, 191.fma3d, 200.sixtrack, 301.apsi)
3 GHz P4:
* ICC: 1298
* NAGware: 658
2 GHz G5 (NAGware): 866
NAGware yields horrid performance for the P4. SPECfp is a computationally bound suite, and the sophistication and level of optimizations a compiler attempts is going to yield a significant difference.
There is only one source for official SPEC results:
spec.org. I suggest waiting until IBM submits official scores for the PPC 970 before attempting to make any comparisons.
So 110% bonus for the 64bit into 130% bonus for efficiancy, gets you 143% per cycle.
143% percent combined with the 160% dual cpu bonus gets you a grand total of
228.8% effeciveness...
But I will have to take away 10% becuase the world is not what it should be. So that's 218% effectiveness clock to clock.
I only wish performance evaluation was so cut-and-dry.
😉