Intel Fully Embracing LLVM For Their C/C++ Compilers

[phoronix]

Phoronix: Intel Fully Embracing LLVM For Their C/C++ Compilers

Intel's next-generation C/C++ compilers are fully leveraging the LLVM compiler stack in place of their former propritary compiler code-base. Intel has "complete[d] adoption" of LLVM moving forward for their C/C++ compiler needs...

https://www.phoronix.com/scan.php?pa...Adoption-C-CPP

[microcode]

Congratulations to Intel on a step toward killing ICC. It is always hard to make a jump like this.

[tildearrow]

Typo:

Phoronix: Intel Fully Embracing LLVM For Their C/C++ Compilers

Intel's next-generation C/C++ compilers are fully leveraging the LLVM compiler stack in place of their former propritary compiler code-base. Intel has "complete[d] adoption" of LLVM moving forward for their C/C++ compiler needs...

https://www.phoronix.com/scan.php?pa...Adoption-C-CPP

[tildearrow]

GCC: the last compiler standing

[ZuseZ4]

GCC: the last compiler standing

Stallman: Hold my beer.

[phoenk]

GCC: the last compiler standing

MSVC still exists too

[tildearrow]

MSVC still exists too

Oops! I forgot!


But LLVM is available as option to use with Visual Studio

[rmfx]

Hoping that the staff working on their compilers will now contribute full steam to llvm, and that it's not a way to just cut costs.

[pipe13]

"Looks like it's time to fire up some new Intel compiler benchmarks on Linux...."

Indeed.

Err... You will include comparisons on both i*Lake and Vermeer, right?

[Ironmask]

What's the purpose of creating another C++ compiler on top of LLVM instead of just contributing to Clang? Are Intel's optimizations too specific/divergent from Clang's architecture?