News for hackers. Stuff that matters.
Re:Gcc Misinterprets Trivial Loop as Infinite by Andys on Saturday July 25, 2009 @03:28AM (#723082)
When I compiled Ruby 1.8.6 with Intel C, it ran benchmarks 5-10% faster than when I compiled with GCC.
Re:Gcc Misinterprets Trivial Loop as Infinite by CrLf on Saturday July 25, 2009 @05:13AM (#723119)
There was a time when icc was really ahead of gcc on Intel processors.

When I worked in the chemistry department of my university, we did some compiler benchmarks on Pentium 4's, AMD Athlons and even some Alphas (gcc vs. compaq compiler in this case). We did this at a time where icc was being touted as best than sliced bread, but found out that while it mostly outperformed gcc on the Pentiums, it did so by a small margin. On the Athlons gcc was faster across the board. On the Alphas, gcc was also better (except on fortran code, where compaq compiler was way better).

And this was gcc 3.x. Since then gcc has evolved quite a bit, and I wouln't be surprised to see it take the performance crown everywhere if I repeated these benchmarks today.

Re:Gcc Misinterprets Trivial Loop as Infinite by gaius on Saturday July 25, 2009 @06:47AM (#723159)
At my last job our (numeric) C and C++ code was in some case twice as fast compiled with SPARCworks (or whatever it's called this week) compared to GCC.

To be fair tho', $vendor can concentrate 100% on $processor, GCC at least tries to be cross-platform.