LLVM 2.2 Release Notes

@@ -35,7 +36,7 @@ RELEASE

This document contains the release notes for the LLVM compiler -infrastructure, release 2.2. Here we describe the status of LLVM, including +infrastructure, release 2.3. Here we describe the status of LLVM, including major improvements from the previous release and any known problems. All LLVM releases may be downloaded from the LLVM releases web site.

@@ -55,111 +56,236 @@ current one. To see the release notes for a specific releases, please see the

- What's New? + Major Changes and Sub-project Status

This is the thirteenth public release of the LLVM Compiler Infrastructure. -It includes many features and refinements from LLVM 2.1.

This is the fourteenth public release of the LLVM Compiler Infrastructure. +It includes a large number of features and refinements from LLVM 2.2.

+ +

-llvm-gcc 4.0, llvm-gcc 4.2, and clang +Major Changes in LLVM 2.3

LLVM 2.2 fully supports both the llvm-gcc 4.0 and llvm-gcc 4.2 front-ends (in -LLVM 2.1, llvm-gcc 4.2 was beta). Since LLVM 2.1, the llvm-gcc 4.2 front-end -has made leaps and bounds and is now at least as good as 4.0 in virtually every -area, and is better in several areas (for example, exception handling -correctness). We strongly recommend that you migrate from llvm-gcc 4.0 to -llvm-gcc 4.2 in this release cycle because LLVM 2.2 is the last release -that will support llvm-gcc 4.0: LLVM 2.3 will only support the llvm-gcc -4.2 front-end.

LLVM 2.3 no longer supports llvm-gcc 4.0, it has been replaced with + llvm-gcc 4.2.

+ +

LLVM 2.3 no longer includes the llvm-upgrade tool. It was useful + for upgrading LLVM 1.9 files to LLVM 2.x syntax, but you can always use a + previous LLVM release to do this. One nice impact of this is that the LLVM + regression test suite no longer depends on llvm-upgrade, which makes it run + faster.

+ +

The llvm2cpp tool has been folded into llc, use + llc -march=cpp instead of llvm2cpp.

The clang project is an effort to build -a set of new 'llvm native' front-end technologies for the LLVM optimizer -and code generator. Currently, its C and Objective-C support is maturing -nicely, and it has advanced source-to-source analysis and transformation -capabilities. If you are interested in building source-level tools for C and -Objective-C (and eventually C++), you should take a look. However, note that -clang is not an official part of the LLVM 2.2 release. If you are interested in -this project, please see the web site.

LLVM API Changes:

Several core LLVM IR classes have migrated to use the + 'FOOCLASS::Create(...)' pattern instead of 'new + FOOCLASS(...)' (e.g. where FOOCLASS=BasicBlock). We hope to + standardize on FOOCLASS::Create for all IR classes in the future, + but not all of them have been moved over yet.
LLVM 2.3 renames the LLVMBuilder and LLVMFoldingBuilder classes to + IRBuilder. +
MRegisterInfo was renamed to + + TargetRegisterInfo.
The MappedFile class is gone, please use + + MemoryBuffer instead.
The '-enable-eh' flag to llc has been removed. Now code should + encode whether it is safe to omit unwind information for a function by + tagging the Function object with the 'nounwind' attribute.
The ConstantFP::get method that uses APFloat now takes one argument + instead of two. The type argument has been removed, and the type is + now inferred from the size of the given APFloat value.

-Major New Features +Other LLVM Sub-Projects

+The core LLVM 2.3 distribution currently consists of code from the core LLVM +repository (which roughly contains the LLVM optimizer, code generators and +supporting tools) and the llvm-gcc repository. In addition to this code, the +LLVM Project includes other sub-projects that are in development. The two which +are the most actively developed are the new vmkit Project +and the Clang Project. +

Dale contributed full support for long double on x86/x86-64 (where it is 80 -bits) and on Darwin PPC/PPC64 (where it is 128 bits).

- -

Ada, gfortran

+ +

+vmkit +

-debug improvements -O0 -EH. +The "vmkit" project is a new addition to the LLVM family. It is an +implementation of a JVM and a CLI Virtual Machines (Microsoft .NET is an +implementation of the CLI) using the Just-In-Time compiler of LLVM.

+ +

The JVM, called JnJVM, executes real-world applications such as Apache +projects (e.g. Felix and Tomcat) and the SpecJVM98 benchmark. It uses the GNU +Classpath project for the base classes. The CLI implementation, called N3, is +its in early stages but can execute simple applications and the "pnetmark" +benchmark. It uses the pnetlib project as its core library.

+ +

The 'vmkit' VMs compare in performance with industrial and top open-source +VMs on scientific applications. Besides the JIT, the VMs use many features of +the LLVM framework, including the standard set of optimizations, atomic +operations, custom function provider and memory manager for JITed methods, and +specific virtual machine optimizations. vmkit is not an official part of LLVM +2.3 release. It is publicly available under the LLVM license and can be +downloaded from: +

-Gordon: GC Revamp. docs/GarbageCollection.html +

svn co http://llvm.org/svn/llvm-project/vmkit/trunk vmkit

-Kaleidescope: docs/tutorial +

+ + +

+Clang +

+ +

The Clang project is an effort to build +a set of new 'LLVM native' front-end technologies for the LLVM optimizer +and code generator. Clang is continuing to make major strides forward in all +areas. Its C and Objective-C parsing support is very solid, and the code +generation support is far enough along to build many C applications. While not +yet production quality, it is progressing very nicely. In addition, C++ +front-end work has started to make significant progress.

+ +

At this point, Clang is most useful if you are interested in source-to-source +transformations (such as refactoring) and other source-level tools for C and +Objective-C. Clang now also includes tools for turning C code into pretty HTML, +and includes a new static +analysis tool in development. This tool focuses on automatically finding +bugs in C and Objective-C code.

+ +

+ + + +

+ What's New? +

+ -Gordon: C and Ocaml Bindings +

LLVM 2.3 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. +

-Optimizer Improvements +Major New Features

Some of the most noticable feature improvements this release have been in the -optimizer, speeding it up and making it more aggressive. For example:

LLVM 2.3 includes several major new capabilities:

The biggest change in LLVM 2.3 is Multiple Return Value (MRV) support. + MRVs allow LLVM IR to directly represent functions that return multiple + values without having to pass them "by reference" in the LLVM IR. This + allows a front-end to generate more efficient code, as MRVs are generally + returned in registers if a target supports them. See the LLVM IR Reference for more details.
+ +
MRVs are fully supported in the LLVM IR, but are not yet fully supported in + on all targets. However, it is generally safe to return up to 2 values from + a function: most targets should be able to handle at least that. MRV + support is a critical requirement for X86-64 ABI support, as X86-64 requires + the ability to return multiple registers from functions, and we use MRVs to + accomplish this in a direct way.
LLVM 2.3 includes a complete reimplementation of the "llvmc" + tool. It is designed to overcome several problems with the original + llvmc and to provide a superset of the features of the + 'gcc' driver.
+ +
The main features of llvmc2 are: +
- Extended handling of command line options and smart rules for + dispatching them to different tools.
- Flexible (and extensible) rules for defining different tools.
- The different intermediate steps performed by tools are represented + as edges in the abstract graph.
- The 'language' for driver behavior definition is tablegen and thus + it's relatively easy to add new features.
- The definition of driver is transformed into set of C++ classes, thus + no runtime interpretation is needed.
+
Daniel Berlin and (Curtis?) rewrote Andersen's alias analysis (which is not -enabled by default) to be several orders of magnitude faster, implmented Offline -Variable Substitution.
LLVM 2.3 includes a completely rewritten interface for Link Time Optimization. This interface + is written in C, which allows for easier integration with C code bases, and + incorporates improvements we learned about from the first incarnation of the + interface.
The Kaleidoscope tutorial now + includes a "port" of the tutorial that uses the Ocaml bindings to implement + the Kaleidoscope language.

-Code Generator Improvements +llvm-gcc 4.2 Improvements

foci of this release was performance tuning and bug - fixing. In addition to these, several new major changes occurred:

LLVM 2.3 fully supports the llvm-gcc 4.2 front-end, and includes support +for the C, C++, Objective-C, Ada, and Fortran front-ends.

llvm-gcc 4.2 includes numerous fixes to better support the Objective-C +front-end. Objective-C now works very well on Mac OS/X.
Owen contributed Machine Loop info, domintors, etc. Merged dom and - postdom.
Fortran EQUIVALENCEs are now supported by the gfortran +front-end.
Dan added support for emitting debug information with .file and .loc on -targets that support it
llvm-gcc 4.2 includes many other fixes which improve conformance with the +relevant parts of the GCC testsuite.
Evan physical register dependencies in the BURR scheduler
Evan EXTRACT_SUBREG coalescing support

@@ -167,7 +293,7 @@ targets that support it

-Target Specific Improvements +LLVM Core Improvements

@@ -175,47 +301,224 @@ targets that support it

Evan X86 now models EFLAGS in instructions.
Evan: If conversion on by default for ARM.
Bruno: MIPS PIC support.
Arnold Schwaighofer: X86 tail call support.
LLVM IR now directly represents "common" linkage, instead of representing it +as a form of weak linkage.
LLVM IR now has support for atomic operations, and this functionality can be +accessed through the llvm-gcc "__sync_synchronize", +"__sync_val_compare_and_swap", and related builtins. Support for +atomics are available in the Alpha, X86, X86-64, and PowerPC backends.
The C and Ocaml bindings have extended to cover pass managers, several +transformation passes, iteration over the LLVM IR, target data, and parameter +attribute lists.

+ +

+Optimizer Improvements +

+ +

In addition to a huge array of bug fixes and minor performance tweaks, the +LLVM 2.3 optimizers support a few major enhancements:

+ +

Loop index set splitting on by default. +This transformation hoists conditions from loop bodies and reduces a loop's +iteration space to improve performance. For example,
+ +
+
```
+for (i = LB; i < UB; ++i)
+  if (i <= NV)
+    LOOP_BODY
+
```
+
+ +
is transformed into:
+ +
+
```
+NUB = min(NV+1, UB)
+for (i = LB; i < NUB; ++i)
+  LOOP_BODY
+
```
+
+
+
LLVM now includes a new memcpy optimization pass which removes +dead memcpy calls, unneeded copies of aggregates, and performs +return slot optimization. The LLVM optimizer now notices long sequences of +consecutive stores and merges them into memcpy's where profitable.
Alignment detection for vector memory references and for memcpy and +memset is now more aggressive.
The Aggressive Dead Code Elimination (ADCE) optimization has been rewritten +to make it both faster and safer in the presence of code containing infinite +loops. Some of its prior functionality has been factored out into the loop +deletion pass, which is safe for infinite loops. The new ADCE pass is +no longer based on control dependence, making it run faster.
The 'SimplifyLibCalls' pass, which optimizes calls to libc and libm + functions for C-based languages, has been rewritten to be a FunctionPass + instead a ModulePass. This allows it to be run more often and to be + included at -O1 in llvm-gcc. It was also extended to include more + optimizations and several corner case bugs were fixed.
LLVM now includes a simple 'Jump Threading' pass, which attempts to simplify + conditional branches using information about predecessor blocks, simplifying + the control flow graph. This pass is pretty basic at this point, but + catches some important cases and provides a foundation to build on.
Several corner case bugs which could lead to deleting volatile memory + accesses have been fixed.
Several optimizations have been sped up, leading to faster code generation + with the same code quality.

+ +

+ + +

+Code Generator Improvements +

+ +

We put a significant amount of work into the code generator infrastructure, +which allows us to implement more aggressive algorithms and make it run +faster:

+ +

The code generator now has support for carrying information about memory + references throughout the entire code generation process, via the + + MachineMemOperand class. In the future this will be used to improve + both pre-pass and post-pass scheduling, and to improve compiler-debugging + output.
The target-independent code generator infrastructure now uses LLVM's + APInt + class to handle integer values, which allows it to support integer types + larger than 64 bits (for example i128). Note that support for such types is + also dependent on target-specific support. Use of APInt is also a step + toward support for non-power-of-2 integer sizes.
LLVM 2.3 includes several compile time speedups for code with large basic + blocks, particularly in the instruction selection phase, register + allocation, scheduling, and tail merging/jump threading.
LLVM 2.3 includes several improvements which make llc's + --view-sunit-dags visualization of scheduling dependency graphs + easier to understand.
The code generator allows targets to write patterns that generate subreg + references directly in .td files now.
memcpy lowering in the backend is more aggressive, particularly for + memcpy calls introduced by the code generator when handling + pass-by-value structure argument copies.
Inline assembly with multiple register results now returns those results + directly in the appropriate registers, rather than going through memory. + Inline assembly that uses constraints like "ir" with immediates now use the + 'i' form when possible instead of always loading the value in a register. + This saves an instruction and reduces register use.
Added support for PIC/GOT style tail calls on X86/32 and initial + support for tail calls on PowerPC 32 (it may also work on PowerPC 64 but is + not thoroughly tested).

+ +

-llvm-gcc Improvements +X86/X86-64 Specific Improvements

New features include: +

New target-specific features include:

.
llvm-gcc's X86-64 ABI conformance is far improved, particularly in the + area of passing and returning structures by value. llvm-gcc compiled code + now interoperates very well on X86-64 systems with other compilers.
Support for Win64 was added. This includes code generation itself, JIT + support, and necessary changes to llvm-gcc.
The LLVM X86 backend now supports the support SSE 4.1 instruction set, and + the llvm-gcc 4.2 front-end supports the SSE 4.1 compiler builtins. Various + generic vector operations (insert/extract/shuffle) are much more efficient + when SSE 4.1 is enabled. The JIT automatically takes advantage of these + instructions, but llvm-gcc must be explicitly told to use them, e.g. with + -march=penryn.
The X86 backend now does a number of optimizations that aim to avoid + converting numbers back and forth from SSE registers to the X87 floating + point stack. This is important because most X86 ABIs require return values + to be on the X87 Floating Point stack, but most CPUs prefer computation in + the SSE units.
The X86 backend supports stack realignment, which is particularly useful for + vector code on OS's without 16-byte aligned stacks, such as Linux and + Windows.
The X86 backend now supports the "sseregparm" options in GCC, which allow + functions to be tagged as passing floating point values in SSE + registers.
Trampolines (taking the address of a nested function) now work on + Linux/X86-64.
__builtin_prefetch is now compiled into the appropriate prefetch + instructions instead of being ignored.
128-bit integers are now supported on X86-64 targets. This can be used + through __attribute__((TImode)) in llvm-gcc.
The register allocator can now rematerialize PIC-base computations, which is + an important optimization for register use.
The "t" and "f" inline assembly constraints for the X87 floating point stack + now work. However, the "u" constraint is still not fully supported.

-LLVM Core Improvements +Other Target Specific Improvements

New features include: +

New target-specific features include:

Devang added LLVMFoldingBuilder.
Dan added support for vector sin, cos, and pow intrinsics.
The LLVM C backend now supports vector code.
The Cell SPU backend includes a number of improvements. It generates better + code and its stability/completeness is improving.

+ +

Other Improvements @@ -226,7 +529,10 @@ targets that support it

.
LLVM now builds with GCC 4.3.
Bugpoint now supports running custom scripts (with the -run-custom + option) to determine how to execute the command and whether it is making + forward process.

@@ -242,20 +548,19 @@ targets that support it

LLVM is known to work on the following platforms:

Intel and AMD machines running Red Hat Linux, Fedora Core and FreeBSD +
Intel and AMD machines (IA32) running Red Hat Linux, Fedora Core and FreeBSD (and probably other unix-like systems).
PowerPC and X86-based Mac OS X systems, running 10.3 and above in 32-bit and 64-bit modes.
Intel and AMD machines running on Win32 using MinGW libraries (native).
Intel and AMD machines running on Win32 with the Cygwin libraries (limited support is available for native builds with Visual C++).
Sun UltraSPARC workstations running Solaris 8.
Sun UltraSPARC workstations running Solaris 10.
Alpha-based machines running Debian GNU/Linux.
Itanium-based machines running Linux and HP-UX.
Itanium-based (IA64) machines running Linux and HP-UX.

The core LLVM infrastructure uses -GNU autoconf to adapt itself +

The core LLVM infrastructure uses GNU autoconf to adapt itself to the machine and operating system on which it is built. However, minor porting may be required to get LLVM to work on new platforms. We welcome your portability patches and reports of successful builds or error messages.

@@ -289,15 +594,13 @@ there isn't already one.

be broken or unreliable, or are in early development. These components should not be relied on, and bugs should not be filed against them, but they may be useful to some people. In particular, if you would like to work on one of these -components, please contact us on the LLVMdev list.

+components, please contact us on the LLVMdev list.

The -cee pass is known to be buggy and will be removed in - LLVM 2.3.
The MSIL, IA64, Alpha, and MIPS backends are experimental.
The LLC "-filetype=asm" (the default) is the only supported +
The MSIL, IA64, Alpha, SPU, and MIPS backends are experimental.
The llc "-filetype=asm" (the default) is the only supported value for this option.
The llvmc tool is not supported.

@@ -310,11 +613,23 @@ components, please contact us on the

The X86 backend does not yet support inline - assembly that uses the X86 floating point stack.
The X86 backend occasionally has alignment - problems on operating systems that don't require 16-byte stack alignment - (including most non-darwin OS's like linux).
The X86 backend does not yet support + all inline assembly that uses the X86 + floating point stack. It supports the 'f' and 't' constraints, but not + 'u'.
The X86 backend generates inefficient floating point code when configured + to generate code for systems that don't have SSE2.
Win64 code generation wasn't widely tested. Everything should work, but we + expect small issues to happen. Also, llvm-gcc cannot build mingw64 runtime + currently due + to several + bugs due to lack of support for the + 'u' inline assembly constraint and X87 floating point inline assembly.
The X86-64 backend does not yet support position-independent code (PIC) + generation on Linux targets.
The X86-64 backend does not yet support the LLVM IR instruction + va_arg. Currently, the llvm-gcc front-end supports variadic + argument constructs on X86-64 by lowering them manually.

llvm-gcc does not support __builtin_apply yet. - See Constructing Calls: Dispatching a call to another function.
-
llvm-gcc partially supports these GCC extensions:
-
1. Nested Functions: - - As in Algol and Pascal, lexical scoping of functions. - Nested functions are supported, but llvm-gcc does not support - taking the address of a nested function (except on the X86-32 target) - or non-local gotos.
2. Function Attributes: - - Declaring that functions have no side effects or that they can never - return.
  - - Supported: alias, always_inline, cdecl, - const, constructor, destructor, - deprecated, fastcall, format, - format_arg, non_null, noinline, - noreturn, pure, regparm - section, stdcall, unused, used, - visibility, warn_unused_result, weak
  - - Ignored: nothrow, malloc, - no_instrument_function
-
llvm-gcc supports the vast majority of GCC extensions, including:
- -
1. Pragmas: Pragmas accepted by GCC.
2. Local Labels: Labels local to a block.
3. Other Builtins: - Other built-in functions.
4. Variable Attributes: - Specifying attributes of variables.
5. Type Attributes: Specifying attributes of types.
6. Thread-Local: Per-thread variables.
7. Variable Length: - Arrays whose length is computed at run time.
8. Labels as Values: Getting pointers to labels and computed gotos.
9. Statement Exprs: Putting statements and declarations inside expressions.
10. Typeof: typeof: referring to the type of an expression.
11. Lvalues: Using ?:, "," and casts in lvalues.
12. Conditionals: Omitting the middle operand of a ?: expression.
13. Long Long: Double-word integers.
14. Complex: Data types for complex numbers.
15. Hex Floats:Hexadecimal floating-point constants.
16. Zero Length: Zero-length arrays.
17. Empty Structures: Structures with no members.
18. Variadic Macros: Macros with a variable number of arguments.
19. Escaped Newlines: Slightly looser rules for escaped newlines.
20. Extended Asm: Assembler instructions with C expressions as operands.
21. Constraints: Constraints for asm operands.
22. Asm Labels: Specifying the assembler name to use for a C symbol.
23. Explicit Reg Vars: Defining variables residing in specified registers.
24. Vector Extensions: Using vector instructions through built-in functions.
25. Target Builtins: Built-in functions specific to particular targets.
26. Subscripting: Any array can be subscripted, even if not an lvalue.
27. Pointer Arith: Arithmetic on void-pointers and function pointers.
28. Initializers: Non-constant initializers.
29. Compound Literals: Compound literals give structures, unions, -or arrays as values.
30. Designated Inits: Labeling elements of initializers.
31. Cast to Union: Casting to union type from any member of the union.
32. Case Ranges: `case 1 ... 9' and such.
33. Mixed Declarations: Mixing declarations and code.
34. Function Prototypes: Prototype declarations and old-style definitions.
35. C++ Comments: C++ comments are recognized.
36. Dollar Signs: Dollar sign is allowed in identifiers.
37. Character Escapes: \e stands for the character <ESC>.
38. Alignment: Inquiring about the alignment of a type or variable.
39. Inline: Defining inline functions (as fast as macros).
40. Alternate Keywords:__const__, __asm__, etc., for header files.
41. Incomplete Enums: enum foo;, with details to follow.
42. Function Names: Printable strings which are the name of the current function.
43. Return Address: Getting the return or frame address of a function.
44. Unnamed Fields: Unnamed struct/union fields within structs/unions.
45. Attribute Syntax: Formal syntax for attributes.

- -

If you run into GCC extensions which have not been included in any of these -lists, please let us know (also including whether or not they work).

If you run into GCC extensions which are not supported, please let us know. +