The Linux Kernel Looks To Drop Support For Intel's ICC Compiler

[CommunityMember]

I believe ICC is based on Clang these days anyway.

About a year ago Intel announced that they moved to the LLVM stack for their compiler, and phoronix picked that up: https://www.phoronix.com/news/Intel-LLVM-Adoption-C-CPP

And IBM announced their move to the LLVM stack about a year before that for their XL compiler suite.

[CochainComplex]

Then work on it and send patches.

back then you had to pay for the ICC and i was not sure how long the it department is going to subscribe for a license (public research facility). Better dont get trapped in the vendor lockin. It was more a "curiosity thing".

[archkde]

Good riddance. Nobody needs a proprietary and non-compliant compiler that puts certain hardware at a disadvantage on purpose, when better alternatives are available.

[szymon_g]

why would a piece of software be dependant on the compiler anyway? if it follows standards, it should be compilable on anything that implements it

[Svyatko]

Another reason: Intel was developing compilers in Russia.
Now Intel Labs closed, Intel website for technical details and drivers are unavailable from Russia.
Twitter website is unavailable (Russian own sanctions for mass media), and many other sites.
There is a big halt for Russian IT.

[phuclv]

why would a piece of software be dependant on the compiler anyway? if it follows standards, it should be compilable on anything that implements it

unfortunately Linux kernel uses a lot of GCC extensions. Clang had to catch up with those extensions and compile options in order to build Linux

[CommunityMember]

why would a piece of software be dependant on the compiler anyway? if it follows standards, it should be compilable on anything that implements it

The Linux kernel was not strictly C standard compliant. The code base was written with gcc-isms, and the build system presumed gcc (and related utilities). Over the years some of those gcc-isms were replaced with C compliant equivalents, and clang/llvm added some acceptance (and some cases ignoring) gcc-isms and compiler flags, but until recently, making the kernel build with anything other than gcc required out-of-tree patches.

[ryao]

Good riddance. Nobody needs a proprietary and non-compliant compiler that puts certain hardware at a disadvantage on purpose, when better alternatives are available.

They claimed to have stopped doing that more than 10 years ago. Also, if I recall correctly, much of what put AMD at a disadvantage was in Intel’s math libraries (which could be used with any compiler), so the blame is misplaced.

[archkde]

They claimed to have stopped doing that more than 10 years ago. Also, if I recall correctly, much of what put AMD at a disadvantage was in Intel’s math libraries (which could be used with any compiler), so the blame is misplaced.

What of that did they stop doing 10 years ago? ICC/ICX is still proprietary; the "optimization notice" was in fact removed, but only pretty recently; and AFAIK, fast-math is still enabled by default.

[ryao]

back then you had to pay for the ICC and i was not sure how long the it department is going to subscribe for a license (public research facility). Better dont get trapped in the vendor lockin. It was more a "curiosity thing".

I remember being able to download it for free around 2011.