A Linux Compiler Deathmatch: GCC, LLVM, DragonEgg, Open64, Etc...
phoronix.com
phoronix.com
http://global.phoronix-test-suite.com/index.php?k=profile...
I think giving each compiler a hue and encoding the optimization level as saturation would have been a useful addition to the spatial organization. Rephrasing the data so that "big = good" would also save much of the mental "what am I looking at?" diversion at each chart view.
Not getting a SPEC license makes this strictly amateur hour. And yes, I know compilers are tuned for SPEC, but you'd at least get repeatable high-quality results on a wide range of different programs.
SPEC isn't necessarily representative of every program out there, but his weird (and small) collection of microbenchmarks and random fragments of code is even less interesting than SPEC.
tcc (tiny c compiler) appears to be really good - it scores very well in both compilation time and execution speed
open64 (added in second batch of tests) also appears very good, for the same reasons
clang is quite slow.
Programs compiled with gcc -O2 often run faster than with -O3.
[1] http://phoronix.com/forums/showthread.php?29090-CompilerDeat...
side-by-side comparisons do however indicate that Clang performed as good or better than ICC or GCC when -O2 is used!
And through the link by yread you can see that clang really performs very well overall.[1]: http://phoronix.com/forums/showthread.php?29090-CompilerDeat...
IMO tcc with support for more architectures is just as viable an alternative to gcc as clang is.
Many of the optimizations that compilers can do nowadays rely on better than an in-order "barely better than a Pentium" CPU.