Post a Comment
I have waited so long for this. It means that Clang finally has reasonable C++ support!
Now I really can't wait until I can compile the Linux kernel with it. That should be even easier, since it is just C, which has been supported quite well for a long time. (I think the problem is all the inline asm and other platform dependent stuff that basically only kernels ever use.)
Just imagine an entire Linux system compiled with Clang/LLVM...
It would take less than half the time as with GCC. Gentoo would actually be usable. 
Download the plugin version of LLVM and find out at http://dragonegg.llvm.org/ . Note: Dragonegg only works on POSIX systems so it won't work on Windows.
Objective-C is already stable and mature, even for the GNU runtime. The only reason the compiler couldn't bootstrap until now is that the compiler was written in C++ that, while it scales better than C and is probably faster than ObjC for this kind of job, requires a complex compiler and libraries to compile at all.
As for GNUStep... Well, it hadn't much following back when it was created, it hasn't now. You can't force people to improve it.
It has support for a lot of them and work is obviously being done at a rapid pace to add support for the rest. You didn't have the foresight to think of compiling Linux before any Clang developer did, you know.
There were a few LLVM features missing necessary to implement certain GCC extensions (and so Clang couldn't even try to implement them), but they are definitely being actively addressed.
I have yet to test it myself:
http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-February/029103.htm...
There is a lot of work being done to get LLVM to the point where it can replace GCC within the *BSD's. Hopefully we'll start to see such a transition within the next couple of years as more components of the *BSD system are replaced with *BSD licensed technologies.
Hopefully there will also be a move to making LLVM the default compiler for Mac OS X in the not too distant future given that there will be better integration between XCode and the compiler so that more fruitful feedback can be given to the developer when something goes pear shaped.
Hopefully there will also be a move to making LLVM the default compiler for Mac OS X in the not too distant future given that there will be better integration between XCode and the compiler so that more fruitful feedback can be given to the developer when something goes pear shaped.
Xcode was built with LLVM 2.6.
I'd expect with the release of LLVM 2.8 and Clang 1.2 or 2.0 [whatever they call it] that the move will be made, though GCC-4.5 obviously is supported via the DragonEgg project as a GCC-4.5-LLVM frontend.
LLVM 2.7 is already being tagged for an end of March release.
Edited 2010-02-06 21:09 UTC
No - it was compiled using LLVM with a GCC front end - what I am talking about is a complete LLVM replacement for the GNU toolchain which is currently in development; not just LLVM but Clang and the GNU bintools replacement which is in development
LLVM 2.7 is already being tagged for an end of March release.
I do hope that there is a push to move developers away from using GNU extensions in favour of using standards based C/C++ - if that means by default displaying big ugly messages that their code is crap and to re-write it in standard C/C++ then hopefully we'll see projects become more platform independent than the current situation of software in the open source world being solely written for Linux.
Edited 2010-02-07 03:11 UTC
No - it was compiled using LLVM with a GCC front end - what I am talking about is a complete LLVM replacement for the GNU toolchain which is currently in development; not just LLVM but Clang and the GNU bintools replacement which is in development
LLVM 2.7 is already being tagged for an end of March release.
I do hope that there is a push to move developers away from using GNU extensions in favour of using standards based C/C++ - if that means by default displaying big ugly messages that their code is crap and to re-write it in standard C/C++ then hopefully we'll see projects become more platform independent than the current situation of software in the open source world being solely written for Linux. "
http://llvm.org/Users.html
Xcode 3.2 (and later): Clang is now included as a production quality C and Objective-C compiler that is available for use in Xcode or from the command line. It supports X86-32/X86-64 and builds code 2-3x faster than GCC in "-O0 -g" mode. Many "developer tools" GUI apps were shipped built with Clang, including Xcode, Interface Builder, Automator, and several others.
Well, there is not really that much "non-BSD" stuff in modern BSD systems. Gcc, linker and binutils, and groff. That's pretty much it. The last one is being replaced AFAIr and the first group presumably goes out if a new compiler is brought in full-time.
http://clang.llvm.org/cxx_status.html
February 5, 2010.
Some libraries (e.g., Boost.MPL) successfully build and pass regression tests, the majority still fail.
http://clang.llvm.org/cxx_status.html
Cmake
Compiles, passes regression tests (debug build) February 9, 2010
Qt
Partially compiles; miscompilation of uic prevents complete compilation, qmake works, some small examples also. February 9, 2010 [Tracking bug: PR5881]
New additions: AST



