To read all comments associated with this story, please click here.
LLVM is part of a compiler infrastructure which works like that
front-end (llvm-gcc, dragonegg, clang) --> Intermediate form (LLVM optimize this) --> Assembly code (x86, arm ..)
LLVM was started as a university research project, Apple then funded this because the switch from GPLv2 to GPLv3 in the gcc project.
The main benefits of llvm for now is the very fast compilation speed (15min for the kernel) and the error reporting which is excellent.
front-end (llvm-gcc, dragonegg, clang) --> Intermediate form (LLVM optimize this) --> Assembly code (x86, arm ..)
LLVM was started as a university research project, Apple then funded this because the switch from GPLv2 to GPLv3 in the gcc project.
The main benefits of llvm for now is the very fast compilation speed (15min for the kernel) and the error reporting which is excellent.
It had less to do with the move from GPL2 to GPL3, it had to do with Apple wanting heavier integration between the compiler and the IDE so that they could provide the sort of debugging that one see's in the likes of Visual Studio. That sort of debugging needs heavy integration between the two and unfortunately it would be a violation of the GPL licence to which GCC is licenced under if Apple linked their proprietary application to GCC.
There are a load of other benefits that have been mentioned in previous conferences they've held - so it is more than just a matter of simply a response to GCC moving from GPL2 to GPL3. On a side note, there has always been a matter of friction between GCC maintainers and Apple in regards to how changes were merged back in. Now that Apple controls the development of LLVM it means it gives them more freedom or when and how they merge changes.
LLVM is a low level virtual machine (hence the name), it is in the simplest form a compiler back-end. This means that it takes code that is parsed from a language (C, C++, whatever) and converts it to a program the computer can read (or an interpreter for that matter).
Clang is the front-end for the c, c++ and objective-c/c++ languages. The combination of LLVM and Clang is equivalent to GCC with the various front-ends for the languages stated above.
Why it exists? Why does anything exist? philosophy aside, basically LLVM is supposed to be more modular than GCC, and LLVM is licensed under the BSD, while GCC is GLP.
The reason that this is interesting is because the Linux kernel has been written with the GCC compiler from the start. Being able to compile, not to mention have the code run somewhat correctly, is a milestone because software like kernels ask a lot out of compilers. Also different compilers may be able to point out problems that were not seen before.
The last thing is that because both compilers conform to an ansi spec, making sure that the kernel builds with both compilers gives better assurance that the kernel code complies with the ansi standard, which cannot hurt.
This is a great starting point
http://llvm.org/
I really want to have a go at creating my own little language for the hang of it, but time does not permit right now. Basically I could write a compiler for a new language that could be built on any number of platforms.
Nice...
Clang is an example of an app build using LLVM...
There's an awesome little example of this here:
http://llvm.org/docs/tutorial/




Member since:
2005-10-11
http://clang.llvm.org/index.html
What is LLVM? Why does it exist? What technology can it be compared to? What benefit does this have to the linux kernel?
Okay I started this post as an idiot. But I would like to know what this LLVM business is.