3 ms·
> t isn't as performant or as well tested as professional compilers I don't know how true this statement is. ICC has been found to be very lacking compared to
by Alupis 12y ago
> t isn't as performant or as well tested as professional compilers
I don't know how true this statement is. ICC has been found to be very lacking compared to both gcc and clang -- and I'd wager in-house testing doesn't compare to massive world-wide deployment of gcc and clang as far as rooting out tough bugs that crop up in weird circumstances.
- michael_h 12y ago> ICC has been found to be very lacking compared to both gcc and clang Who found that? For processing intensive tasks, I routinely get a 30% reduction in run time using ICC - mainly owing to ICC's aggressive vectorization. Rarely, I'll have to do some shenanigans to force it to work correctly. Very rarely. I use clang when developing because the error messages are miles ahead of anybody else, then produce a 'stable' GCC version and an ICC version. If the ICC version produces the same results as the GCC version for the test suite, I exclusively use the ICC version.
- Joky 12y ago"processing intensive tasks" may not be the one to expose all the corner cases of C and C++?
- gh02t 12y agoIn my experience, `icc/pc` and `ifort` give a significant speed boost for numerical code (on Intel hardware at least), but for more general purpose code it's not really very impressive. However, the related products like `ipp` and `mkl` are where Intel has a real advantage. My experience has been that `mkl` in particular is dramatically faster than vanilla LAPACK and friends and still quite a bit faster than more optimized variants like ATLAS. But, you don't need to use the Intel compilers to use those libraries, you can use them with gcc as well.
- chisleu 12y agoMy professor in college made the statement and his class said "oh yeah right GCC is everywhere". He spent the break writing tests for GCC and found errors in it's parse tree. He submitted bugs and patches cause good guy coder.