New LLVM C++ Standard Library(blog.llvm.org)
blog.llvm.org
New LLVM C++ Standard Library
http://blog.llvm.org/2010/05/new-libc-c-standard-library.html
10 comments
Apple is systematically cutting their dependence on GCC and related code. I wonder if it's due to GPLv3 or some other reason.
Among other reasons, I'd guess this is Apple's attempt at modernization. The GCC/libc/libstdc++ codebase has been around for ages, and has accumulated cruft. Starting from scratch isn't always a solution, but in cases like this I think it can be.
Modernizing the compiler (via clang/LLVM) is a great step forward, but modernizing the C++ libraries to take advantage of the new compiler infrastructure is a sensible step 2. If they can in fact speed up compilation speed and memory requirements (both at compile-time and run-time), as well as providing link-time and run-time optimization, it could be a big win, especially for large C++ projects (such as Mozilla, KDE, Qt, etc.).
Modernizing the compiler (via clang/LLVM) is a great step forward, but modernizing the C++ libraries to take advantage of the new compiler infrastructure is a sensible step 2. If they can in fact speed up compilation speed and memory requirements (both at compile-time and run-time), as well as providing link-time and run-time optimization, it could be a big win, especially for large C++ projects (such as Mozilla, KDE, Qt, etc.).
I would imagine a lot of it involves improving xcode by using the same code for compiler and IDE. GPL2 or GPL3 really doesn't make much of a difference in this regard.
Although the GPL3 question comes up with the non-inclusion of a newer version of Samba in OS X Server. This is making it hard / impossible to add Win 7 to a network with a OS X Server PDC.
Although the GPL3 question comes up with the non-inclusion of a newer version of Samba in OS X Server. This is making it hard / impossible to add Win 7 to a network with a OS X Server PDC.
I would imagine that's the case. Either way, its nice to see llvm's c++ support coming along.
With in-house processor design (Intrinsity), perhaps secrecy (and anti-jailbreak) is their aim:
In this scenario, they want to be able to ship an XCode and iPhoo SDK without having to distribute the source to their code generator.
In this scenario, they want to be able to ship an XCode and iPhoo SDK without having to distribute the source to their code generator.
i was surprised they didn't base it upon Apache Stdcxx, if they were just trying to avoid the GPL:
http://stdcxx.apache.org/
I merely glanced at bits of the code without diving into the implementation that much, but my high-level thoughts:
+ I love the "synopsis" header in front of all the classes.
+ I find the style horrible, but still more readable than the SGI-based STL headers. This is a very good thing.
+ Only one developer currently? I wonder how many bugs are yet to be found in this code. Making it ABI-compatible with libstdc++ should make the "swap it in, does it crash?" test very easy.
+ I love the "synopsis" header in front of all the classes.
+ I find the style horrible, but still more readable than the SGI-based STL headers. This is a very good thing.
+ Only one developer currently? I wonder how many bugs are yet to be found in this code. Making it ABI-compatible with libstdc++ should make the "swap it in, does it crash?" test very easy.
Could someone explain: As a person who uses Apple products but doesn't code, what does this mean for me? Is Apple already using this compiler with OS X? Does it mean faster and smaller binaries down the line?
Or is it mostly cool stuff for coders, but mostly transparent for end-users?
Or is it mostly cool stuff for coders, but mostly transparent for end-users?
Is Apple already using this compiler with OS X?
Its in use for some products in Snow Leopard; Xcode, OpenGL, (and, I believe) OpenCL and Automator are built with Clang.
Or is it mostly cool stuff for coders, but mostly transparent for end-users?
Mostly, this. However, the cool things it gives are subtly passed onto the user. For example, LLVM and Clang have a nice static analyzer to help developers find and fix memory leaks. There are other optimizations (for the size of the binary and speed of the program being run) that LLVM is working on, but they're not ready for primetime yet (or weren't, the last time I looked).
Its in use for some products in Snow Leopard; Xcode, OpenGL, (and, I believe) OpenCL and Automator are built with Clang.
Or is it mostly cool stuff for coders, but mostly transparent for end-users?
Mostly, this. However, the cool things it gives are subtly passed onto the user. For example, LLVM and Clang have a nice static analyzer to help developers find and fix memory leaks. There are other optimizations (for the size of the binary and speed of the program being run) that LLVM is working on, but they're not ready for primetime yet (or weren't, the last time I looked).
Thanks!