Re:Intel's “cripple AMD” function (2019)
by outworlder on Friday August 28, 2020 @06:59PM
(#24311344)
I have been hearing about the superiority of Intel's compiler for a couple of decades now. Back when GCC was a tiny baby compared to what it is now, and when Clang/LLVM didn't even exist.
I wonder if this Intel compiler 'superiority' is still the case today, or if this is just a meme at this point.
For matrix manipulation based Fortran scientific codes, ifort/MKL can give +30% compared to gfortran. It's difficult to disentangle where the speedup comes from, but certainly as jedbrown aludes to, the Intel compilers seem to make a better go of poorly optimised / badly written code.
For C based software, its a much closer run thing, and often sticking with GCC avoids weird segfaults when mixing Intel and GCC-compiled Linux libraries.
> This is an overstatement.
To be generous...
Where do you typically see lack of inlining and vectorization with GCC? I'm curious because most times people have said GCC wouldn't vectorize code that I've been able to try, it would, at least if allowed -ffast-math a la Intel (as in BLIS now).
Can you explain "BLIS is used by AMD"? In what way do they use it?
Re:Intel's “cripple AMD” function (2019)
by jedbrown on Saturday August 29, 2020 @09:23AM
(#24315890)
It's their official BLAS [1] since 2015 when they moved away from their proprietary ACML implementation [2].
[1]https://developer.amd.com/amd-aocl/blas-library/
[2] https://developer.amd.com/open-source-strikes-again-accelera...
BLIS is used by AMD and is a good open alternative to MKL (for BLAS) across many platforms. https://github.com/flame/blis/blob/master/docs/Performance.m...