This document contains the release notes for the LLVM Compiler Infrastructure, release 3.0. Here we describe the status of LLVM, including major improvements from the previous release, improvements in various subprojects of LLVM, and some of the current users of the code. All LLVM releases may be downloaded from the LLVM releases web site.
For more information about LLVM, including information about the latest release, please check out the main LLVM web site. If you have questions or comments, the LLVM Developer's Mailing List is a good place to send them.
Note that if you are reading this file from a Subversion checkout or the main LLVM web page, this document applies to the next release, not the current one. To see the release notes for a specific release, please see the releases page.
The LLVM 3.0 distribution currently consists of code from the core LLVM repository (which roughly includes the LLVM optimizers, code generators and supporting tools), and the Clang repository. In addition to this code, the LLVM Project includes other sub-projects that are in development. Here we include updates on these subprojects.
Clang is an LLVM front end for the C, C++, and Objective-C languages. Clang aims to provide a better user experience through expressive diagnostics, a high level of conformance to language standards, fast compilation, and low memory use. Like LLVM, Clang provides a modular, library-based architecture that makes it suitable for creating or integrating with other development tools. Clang is considered a production-quality compiler for C, Objective-C, C++ and Objective-C++ on x86 (32- and 64-bit), and for Darwin/ARM targets.
In the LLVM 3.0 time-frame, the Clang team has made many improvements:
If Clang rejects your code but another compiler accepts it, please take a look at the language compatibility guide to make sure this is not intentional or a known issue.
DragonEgg is a gcc plugin that replaces GCC's optimizers and code generators with LLVM's. It works with gcc-4.5 or gcc-4.6, targets the x86-32 and x86-64 processor families, and has been successfully used on the Darwin, FreeBSD, KFreeBSD, Linux and OpenBSD platforms. It fully supports Ada, C, C++ and Fortran. It has partial support for Go, Java, Obj-C and Obj-C++.
The 3.0 release has the following notable changes:
The new LLVM compiler-rt project is a simple library that provides an implementation of the low-level target-specific hooks required by code generation and other runtime components. For example, when compiling for a 32-bit target, converting a double to a 64-bit unsigned integer is compiled into a runtime call to the "__fixunsdfdi" function. The compiler-rt library provides highly optimized implementations of this and other low-level routines (some are 3x faster than the equivalent libgcc routines).
In the LLVM 3.0 timeframe, the target specific ARM code has converted to "unified" assembly syntax, and several new functions have been added to the library.
LLDB is a ground-up implementation of a command line debugger, as well as a debugger API that can be used from other applications. LLDB makes use of the Clang parser to provide high-fidelity expression parsing (particularly for C++) and uses the LLVM JIT for target support.
Like compiler_rt, libc++ is now dual licensed under the MIT and UIUC license, allowing it to be used more permissively.
Libc++ has been ported to FreeBSD and imported into the base system. It is planned to be the default STL implementation for FreeBSD 10.
The VMKit project is an implementation of a Java Virtual Machine (Java VM or JVM) that uses LLVM for static and just-in-time compilation.
In the LLVM 3.0 time-frame, VMKit has had significant improvements on both runtime and startup performance:
LLBrowse is an interactive viewer for LLVM modules. It can load any LLVM module and displays its contents as an expandable tree view, facilitating an easy way to inspect types, functions, global variables, or metadata nodes. It is fully cross-platform, being based on the popular wxWidgets GUI toolkit.
An exciting aspect of LLVM is that it is used as an enabling technology for a lot of other language and tools projects. This section lists some of the projects that have already been updated to work with LLVM 3.0.
AddressSanitizer uses compiler instrumentation and a specialized malloc library to find C/C++ bugs such as use-after-free and out-of-bound accesses to heap, stack, and globals. The key feature of the tool is speed: the average slowdown introduced by AddressSanitizer is less than 2x.
Clam AntiVirus is an open source (GPL) anti-virus toolkit for UNIX, designed especially for e-mail scanning on mail gateways.
Since version 0.96 it has bytecode signatures that allow writing detections for complex malware. It uses LLVM's JIT to speed up the execution of bytecode on X86, X86-64, PPC32/64, falling back to its own interpreter otherwise. The git version was updated to work with LLVM 3.0.
clang_complete is a VIM plugin, that provides accurate C/C++ autocompletion using the clang front end. The development version of clang complete, can directly use libclang which can maintain a cache to speed up auto completion.
clReflect is a C++ parser that uses clang/LLVM to derive a light-weight reflection database suitable for use in game development. It comes with a very simple runtime library for loading and querying the database, requiring no external dependencies (including CRT), and an additional utility library for object management and serialisation.
Cling is an interactive compiler interface (aka C++ interpreter). It supports C++ and C, and uses LLVM's JIT and the Clang parser. It has a prompt interface, runs source files, calls into shared libraries, prints the value of expressions, even does runtime lookup of identifiers (dynamic scopes). And it just behaves like one would expect from an interpreter.
Crack aims to provide the ease of development of a scripting language with the performance of a compiled language. The language derives concepts from C++, Java and Python, incorporating object-oriented programming, operator overloading and strong typing.
Eero is a fully header-and-binary-compatible dialect of Objective-C 2.0, implemented with a patched version of the Clang/LLVM compiler. It features a streamlined syntax, Python-like indentation, and new operators, for improved readability and reduced code clutter. It also has new features such as limited forms of operator overloading and namespaces, and strict (type-and-operator-safe) enumerations. It is inspired by languages such as Smalltalk, Python, and Ruby.
FAUST is a compiled language for real-time audio signal processing. The name FAUST stands for Functional AUdio STream. Its programming model combines two approaches: functional programming and block diagram composition. In addition with the C, C++, Java output formats, the Faust compiler can now generate LLVM bitcode, and works with LLVM 2.7-3.0.
GHC is an open source, state-of-the-art programming suite for Haskell, a standard lazy functional programming language. It includes an optimizing static compiler generating good code for a variety of platforms, together with an interactive system for convenient, quick development.
GHC 7.0 and onwards include an LLVM code generator, supporting LLVM 2.8 and later. Since LLVM 2.9, GHC now includes experimental support for the ARM platform with LLVM 3.0.
gwXscript is an object oriented, aspect oriented programming language which can create both executables (ELF, EXE) and shared libraries (DLL, SO, DYNLIB). The compiler is implemented in its own language and translates scripts into LLVM-IR which can be optimized and translated into native code by the LLVM framework. Source code in gwScript contains definitions that expand the namespaces. So you can build your project and simply 'plug out' features by removing a file. The remaining project does not leave scars since you directly separate concerns by the 'template' feature of gwX. It is also possible to add new features to a project by just adding files and without editing the original project. This language is used for example to create games or content management systems that should be extendable.
gwXscript is strongly typed and offers comfort with its native types string, hash and array. You can easily write new libraries in gwXscript or native code. gwXscript is type safe and users should not be able to crash your program or execute malicious code except code that is eating CPU time.
is a tool to ensure that a file directly
.h files that provide a symbol that the file uses. It also
#includes from source files.
ispc is a compiler for "single program, multiple data" (SPMD) programs. It compiles a C-based SPMD programming language to run on the SIMD units of CPUs; it often delivers 5-6x speedups on a single core of a CPU with an 8-wide SIMD unit compared to serial code, while still providing a clean and easy-to-understand programming model. For an introduction to the language and its performance, see the walkthrough of a short example program. ispc is licensed under the BSD license.
Julia is a high-level, high-performance dynamic language for technical computing. It provides a sophisticated compiler, distributed parallel execution, numerical accuracy, and an extensive mathematical function library. The compiler uses type inference to generate fast code without any type declarations, and uses LLVM's optimization passes and JIT compiler. The language is designed around multiple dispatch, giving programs a large degree of flexibility. It is ready for use on many kinds of problems.
LanguageKit is a framework for implementing dynamic languages sharing an object model with Objective-C. It provides static and JIT compilation using LLVM along with its own interpreter. Pragmatic Smalltalk is a dialect of Smalltalk, built on top of LanguageKit, that interfaces directly with Objective-C, sharing the same object representation and message sending behaviour. These projects are developed as part of the Étoilé desktop environment.
LuaAV is a real-time audiovisual scripting environment based around the Lua language and a collection of libraries for sound, graphics, and other media protocols. LuaAV uses LLVM and Clang to JIT compile efficient user-defined audio synthesis routines specified in a declarative syntax.
An open source, cross-platform implementation of C# and the CLR that is binary compatible with Microsoft.NET. Has an optional, dynamically-loaded LLVM code generation backend in Mini, the JIT compiler.
Note that we use a Git mirror of LLVM with some patches.
Polly is an advanced data-locality optimizer and automatic parallelizer. It uses an advanced, mathematical model to calculate detailed data dependency information which it uses to optimize the loop structure of a program. Polly can speed up sequential code by improving memory locality and consequently the cache use. Furthermore, Polly is able to expose different kind of parallelism which it exploits by introducing (basic) OpenMP and SIMD code. A mid-term goal of Polly is to automatically create optimized GPU code.
Portable OpenCL is an open source implementation of the OpenCL standard which can be easily adapted for new targets. One of the goals of the project is improving performance portability of OpenCL programs, avoiding the need for target-dependent manual optimizations. A "native" target is included, which allows running OpenCL kernels on the host (CPU).
Pure is an algebraic/functional programming language based on term rewriting. Programs are collections of equations which are used to evaluate expressions in a symbolic fashion. The interpreter uses LLVM as a backend to JIT-compile Pure programs to fast native code. Pure offers dynamic typing, eager and lazy evaluation, lexical closures, a hygienic macro system (also based on term rewriting), built-in list and matrix support (including list and matrix comprehensions) and an easy-to-use interface to C and other programming languages (including the ability to load LLVM bitcode modules, and inline C, C++, Fortran and Faust code in Pure programs if the corresponding LLVM-enabled compilers are installed).
Pure version 0.48 has been tested and is known to work with LLVM 3.0 (and continues to work with older LLVM releases >= 2.5).
Renderscript is Android's advanced 3D graphics rendering and compute API. It provides a portable C99-based language with extensions to facilitate common use cases for enhancing graphics and thread level parallelism. The Renderscript compiler frontend is based on Clang/LLVM. It emits a portable bitcode format for the actual compiled script code, as well as reflects a Java interface for developers to control the execution of the compiled bitcode. Executable machine code is then generated from this bitcode by an LLVM backend on the device. Renderscript is thus able to provide a mechanism by which Android developers can improve performance of their applications while retaining portability.
SAFECode is a memory safe C/C++ compiler built using LLVM. It takes standard, unannotated C/C++ code, analyzes the code to ensure that memory accesses and array indexing operations are safe, and instruments the code with run-time checks when safety cannot be proven statically. SAFECode can be used as a debugging aid (like Valgrind) to find and repair memory safety bugs. It can also be used to protect code from security attacks at run-time.
The Stupid D Compiler is a project seeking to write a self-hosting compiler for the D programming language without using the frontend of the reference compiler (DMD).
TCE is a toolset for designing application-specific processors (ASP) based on the Transport triggered architecture (TTA). The toolset provides a complete co-design flow from C/C++ programs down to synthesizable VHDL and parallel program binaries. Processor customization points include the register files, function units, supported operations, and the interconnection network.
TCE uses Clang and LLVM for C/C++ language support, target independent optimizations and also for parts of code generation. It generates new LLVM-based code generators "on the fly" for the designed TTA processors and loads them in to the compiler backend as runtime libraries to avoid per-target recompilation of larger parts of the compiler chain.
Tart is a general-purpose, strongly typed programming language designed for application developers. Strongly inspired by Python and C#, Tart focuses on practical solutions for the professional software developer, while avoiding the clutter and boilerplate of legacy languages like Java and C++. Although Tart is still in development, the current implementation supports many features expected of a modern programming language, such as garbage collection, powerful bidirectional type inference, a greatly simplified syntax for template metaprogramming, closures and function literals, reflection, operator overloading, explicit mutability and immutability, and much more. Tart is flexible enough to accommodate a broad range of programming styles and philosophies, while maintaining a strong commitment to simplicity, minimalism and elegance in design.
ThreadSanitizer is a data race detector for (mostly) C and C++ code, available for Linux, Mac OS and Windows. On different systems, we use binary instrumentation frameworks (Valgrind and Pin) as frontends that generate the program events for the race detection algorithm. On Linux, there's an option of using LLVM-based compile-time instrumentation.
This release includes a huge number of bug fixes, performance tweaks and minor improvements. Some of the major improvements and new features are listed in this section.
LLVM 3.0 includes several major changes and big features:
LLVM IR has several new features for better support of new targets and that expose new optimization opportunities:
In addition to many minor performance tweaks and bug fixes, this release includes a few major enhancements and additions to the optimizers:
__builtin_expectcalls. That information is currently used for register spill placement and if-conversion, with additional optimizations planned for future releases. The same framework is intended for eventual use with profile-guided optimization.
The LLVM Machine Code (aka MC) subsystem was created to solve a number of problems in the realm of assembly, disassembly, object file format handling, and a number of other related areas that CPU instruction-set level tools work in. For more information, please see the Intro to the LLVM MC Project Blog Post.
We have put a significant amount of work into the code generator infrastructure, which allows us to implement more aggressive algorithms and make it run faster:
setExecutionDomainhooks to use the pass.
New features and major changes in the X86 target include:
-mavxto the compiler. AVX2 implementation is underway on mainline.
@llvm.x86.sse42.crc64.[8|64]. They have been renamed to
New features of the ARM target include:
This release has seen major new work on just about every aspect of the MIPS backend. Some of the major new features include:
The PTX back-end is still experimental, but is fairly usable for compute kernels in LLVM 3.0. Most scalar arithmetic is implemented, as well as intrinsics to access the special PTX registers and sync instructions. The major missing pieces are texture/sampler support and some vector operations.
That said, the backend is already being used for domain-specific languages and can be used by Clang to compile OpenCL C code into PTX.
-mcpu=mblaze3and the 5-stage pipeline model can be selected with
If you're already an LLVM user or developer with out-of-tree changes based on LLVM 2.9, this section lists some "gotchas" that you may run into upgrading from the previous release.
LLVMCmeta compiler driver was removed.
TailDuppass was not used in the standard pipeline and was unable to update ssa form, so it has been removed.
store volatile". The old syntax ("
volatile store") is still accepted, but is now considered deprecated and will be removed in 3.1.
llvm.atomic.*) are now gone. Please use the new atomic instructions, described in the atomics guide.
In addition, many APIs have changed in this release. Some of the major LLVM API changes are:
OpaqueTypeare gone, and all APIs deal with
const Type*. If you need to create recursive structures, then create a named structure, and use
setBody()when all its elements are built. Type merging and refining is gone too: named structures are not merged with other structures, even if their layout is identical. (of course anonymous structures are still uniqued by layout).
PHINode::reserveOperandSpacehas been removed. Instead, you must specify how many operands to reserve space for when you create the PHINode, by passing an extra argument into
ArrayRefinstead of either a pair of pointers (or iterators) to the beginning and end of a range, or a pointer and a length. Others now return an
ArrayRefinstead of a reference to a
std::vector. These include:
StringMap::getOrCreateValuehave been remove except for the one which takes a
LLVMBuildUnwindfunction from the C API was removed. The LLVM
unwindinstruction has been deprecated for a long time and isn't used by the current front-ends. So this was removed during the exception handling rewrite.
LLVMAddLowerSetJmpPassfunction from the C API was removed because the
LowerSetJmppass was removed.
DIBuilderinterface used by front ends to encode debugging information in the LLVM IR now expects clients to use
DIBuilder::finalize()at the end of translation unit to complete debugging information encoding.
LLVM is generally a production quality compiler, and is used by a broad range of applications and shipping in many products. That said, not every subsystem is as mature as the aggregate, particularly the more obscure targets. If you run into a problem, please check the LLVM bug database and submit a bug if there isn't already one or ask on the LLVMdev list.
Known problem areas include:
A wide variety of additional information is available on the LLVM web page, in particular in the documentation section. The web page also contains versions of the API documentation which is up-to-date with the Subversion version of the source code. You can access versions of these documents specific to this release by going into the "llvm/doc/" directory in the LLVM tree.
If you have any questions or comments about LLVM, please feel free to contact us via the mailing lists.