OpenBSD uses Clang on amd64/i386 now.
 

Hooray!

Modern times.

It's been used for arm64 for a while now I believe.

I don't know if it's anything to celebrate. GCC has served us well and it's a credit to RMS that it's been so widely adopted. At least it's completely free of "corporate interests", the same cannot be said of LLVM/clang.

Time will tell I suppose.

The GPLv3 is discouraged on OpenBSD as far as I know.

Plus, it is, at least, questionable if GCC or Clang produce better binaries. Adoption should not be the main reason.

Regarding GPL code in OpenBSD: https://www.linuxquestions.org/quest...9/#post5727227

Apparently clang has advantages over GCC. This message by Eric S. Raymond from a few years ago goes into a few of the whys and wherefores of clang and GCC (in reply to RMS): https://gcc.gnu.org/ml/gcc/2014-01/msg00209.html

This is part of its long term migration from ports, for use with ports... to the base, for use with base. It was already in base, and has been the compiler for arm64.

I CANNOTTTTTTT BELIEVEEEE IT !!! REALLY ???

BSD HAS NOTHING TO DO WITH LINUX (IN TERMS OF COMPILER !!, and beside Ethics). This is really a very big news.

THIS WILL NEVER HAPPEN ON LINUX EVER !

Nobody mentioned Linux here. Please take your tongue off the Shift key.

Better not to mention. Indeed. Sorry.


Man, Holy Respect to BSD !!

Nothing to say, BSD was, is and will be forever the best.

FreeBSD already uses clang as the default compiler (for x86 and arm architectures since 10-RELEASE as I recall?).

OpenBSD has stuck with GCC, while alternatives have been considered. PCC looked promising for a while, but ultimately the project stalled.

I should also correct myself here
This is not strictly true.

Port transition has been smooth - and that's been something to see. Particularly, due to how multiple c++ standard libraries were selected -- or mis-selected -- as the OS has had multiple versions of gcc (in base, in ports) to manage. It is somewhat simplified, now.

Briefly, a small set of compiler / library selection environment variables were added to the port infrastructure, and bulk updates were performed on the affected ports. I updated one of my Qt-based ports this morning, and I could completely ignore the underlying compiler and library changes. :)

Words of wisdom. ;)

Nothing else than truth... Hopefully it will last long enough as an Unix great engineering Empire. :D