clang 2.8 is a "production-quality compiler for [...] C++"

IncredibleLaser · 2010-10-06 22:51:37

According to the release notes, clang "is now feature-complete with respect to the ISO C++ 1998 and 2003 standards". Has anyone tested this on any project using c++ yet? I'd love to see results. Is it possible to use clang as a drop-in replacement for gcc/g++ when compiling using makepkg?

Allan · 2010-10-06 23:01:07

Most software will let you export these in your environment:

CC=clang
CXX=clang++

and then makepkg will happily use clang rather than gcc.

IncredibleLaser · 2010-10-06 23:09:22

Thanks, I tried adding something similiar into my makepkg.conf, but I thought that it didn't work out. I'll do more testing on friday.

falconindy · 2010-10-07 01:25:52

I'm seeing conflicting info... this page (last updated less than a month ago) claims:

Clang currently implements all of the ISO C++ 1998 standard (including the defects addressed in the ISO C++ 2003 standard) except for 'export' (which has been removed from the C++'0x draft). However, the implementation of Clang C++ is still somewhat immature, with remaining bugs that may cause compiler crashes, erroneous errors and warnings, or miscompiled code.

IncredibleLaser · 2010-10-07 07:03:17

I took all my information from here.

kazuo · 2010-10-07 08:47:55

IncredibleLaser wrote:

According to the release notes, clang "is now feature-complete with respect to the ISO C++ 1998 and 2003 standards". Has anyone tested this on any project using c++ yet? I'd love to see results. Is it possible to use clang as a drop-in replacement for gcc/g++ when compiling using makepkg?

Uhh, this remember me a quote :

Loren Merritt wrote:

<pengvado> that brings back the memory:
<pengvado> windows is posix compliant
<pengvado> every single posix function returns ENOTIMPLEMENTED, which is one complying implementation

Something like this can be happening with clang, its feature-complete (i.e. implement all that is needed), but the features are not really complete (i.e. they don't work/are buged)

Rip-Rip · 2010-10-07 17:50:41

Since clang++ can compile Boost and pass the test suite, it can be qualified as "stable and working C++ compiler"

skottish · 2010-12-19 18:01:28

Related bump...

I just noticed that clang can now compile x264 passing off the necessary bits to YASM. x264 is always a simple and good test of the "state of things" in that it's hyper-optimized for the capabilities of hardware. In fact, x264, FFmpeg, and Mplayer all build and run. Is the compiler sane? I don't know yet, but it's a step forward for the project.

Last edited by skottish (2010-12-19 18:02:00)

Arch Linux

#1 2010-10-06 22:51:37

clang 2.8 is a "production-quality compiler for [...] C++"

#2 2010-10-06 23:01:07

Re: clang 2.8 is a "production-quality compiler for [...] C++"

#3 2010-10-06 23:09:22

Re: clang 2.8 is a "production-quality compiler for [...] C++"

#4 2010-10-07 01:25:52

Re: clang 2.8 is a "production-quality compiler for [...] C++"

#5 2010-10-07 07:03:17

Re: clang 2.8 is a "production-quality compiler for [...] C++"

#6 2010-10-07 08:47:55

Re: clang 2.8 is a "production-quality compiler for [...] C++"

#7 2010-10-07 17:50:41

Re: clang 2.8 is a "production-quality compiler for [...] C++"

#8 2010-12-19 18:01:28

Re: clang 2.8 is a "production-quality compiler for [...] C++"

Board footer