I think compile times should only be used as a test workload when comparing computers; using compile times to benchmark compilers is useless to most people (99%? more?).
When building these tests, is there a way to also build and affect the C runtime library. While I can appreciate that many of these tests have "hard stuff" in their code, the performance of an app is always so dependent on the performance of it's underlying runtime library (for things like memcpy, strcmp, etc.) that I think it's worth a look.
I think the description of llvm-gcc is incorrect. llvm-gcc back end is not a modified version of gcc, it's llvm. llvm-gcc front end is a modified version of gcc front end. Please confirm.
And the results were really insightful.
Do a test of GCC vs Intel compiler and/or any other compiler. Compile time speed, run time speed, code size ... hmm..
I wonder how long it takes until Gentoo migrates to clang... Faster compile speed should be crucial there.
Can you guys do a comparison of modern gcc and llvm with Visual Studio and Intel's compiler? It would be interesting to see where the open source compilers are against the proprietary