This document contains the release notes for the LLVM compiler infrastructure, release 2.0. Here we describe the status of LLVM, including any known problems and major improvements from the previous release. 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 CVS or the main LLVM web page, this document applies to the next release, not the current one. To see the release notes for the current or previous releases, see the releases page.

This is the eleventh public release of the LLVM Compiler Infrastructure. Being the first major release since 1.0, this release is different in several ways from our previous releases:

1. We took this as an opportunity to break backwards compatibility with the LLVM 1.x bytecode and .ll file format. If you have LLVM 1.9 .ll files that you would like to upgrade to LLVM 2.x, we recommend the use of the stand alone llvm-upgrade tool. We intend to keep compatibility with .ll and .bc formats within the 2.x release series, like we did within the 1.x series.
2. There are several significant change to the LLVM IR and internal APIs, such as a major overhaul of the type system, the completely new bitcode file format, etc.
3. We designed the release around a 6 month release cycle instead of the usual 3-month cycle. This gave us extra time to develop and test some of the more invasive features in this release.
4. LLVM 2.0 no longer supports the llvm-gcc3 front-end.

Note that while this is a major version bump, this release has been extensively tested on a wide range of software. It is easy to say that this is our best release yet, in terms of both features and correctness.

The mid-level optimizer is now faster and produces better code in many cases. Significant changes include:

The LLVM Target-Independent code generator now supports more target features and optimizes many cases more aggressively. New features include:

In addition, the LLVM target description format has itself been extended in several ways:

Further, several significant target-specific enhancements are included in LLVM 2.0:

More specific changes include:

LLVM is known to work on the following platforms:

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

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.

This section contains all known problems with the LLVM system, listed by component. As new problems are discovered, they will be added to these sections. If you run into a problem, please check the LLVM bug database and submit a bug if there isn't already one.

The following components of this LLVM release are either untested, known to 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.

• The -cee pass is known to be buggy, and may be removed in in a future release.
• C++ EH support
• The IA64 code generator is experimental.
• The Alpha JIT is experimental.
• "-filetype=asm" (the default) is the only supported value for the -filetype llc option.

• The X86 backend does not yet support inline assembly that uses the X86 floating point stack.

• PowerPC backend does not correctly implement ordered FP comparisons.

• The SPARC backend only supports the 32-bit SPARC ABI (-m32), it does not support the 64-bit SPARC ABI (-m64).

• The C back-end produces code that violates the ANSI C Type-Based Alias Analysis rules. As such, special options may be necessary to compile the code (for example, GCC requires the -fno-strict-aliasing option). This problem probably cannot be fixed.
• Zero arg vararg functions are not supported. This should not affect LLVM produced by the C or C++ frontends.
• The C backend does not correctly implement the llvm.stacksave or llvm.stackrestore intrinsics. This means that some code compiled by it can run out of stack space if they depend on these (e.g. C99 varargs).
• The C backend does not support inline assembly code.

• On 21164s, some rare FP arithmetic sequences which may trap do not have the appropriate nops inserted to ensure restartability.

• C++ programs are likely to fail on IA64, as calls to setjmp are made where the argument is not 16-byte aligned, as required on IA64. (Strictly speaking this is not a bug in the IA64 back-end; it will also be encountered when building C++ programs using the C back-end.)
• The C++ front-end does not use IA64 ABI compliant layout of v-tables. In particular, it just stores function pointers instead of function descriptors in the vtable. This bug prevents mixing C++ code compiled with LLVM with C++ objects compiled by other C++ compilers.
• There are a few ABI violations which will lead to problems when mixing LLVM output with code built with other compilers, particularly for floating-point programs.
• Defining vararg functions is not supported (but calling them is ok).
• The Itanium backend has bitrotted somewhat.

• The Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6 processors, any thumb program compiled with LLVM crashes or produces wrong results. (PR1388)
• Compilation for ARM Linux OABI (old ABI) is supported, but not fully tested.

• In the JIT, dlsym() on a symbol compiled by the JIT will not work.

llvm-gcc4 is far more stable and produces better code than llvm-gcc3, but does not currently support Link-Time Optimization or C++ Exception Handling, which llvm-gcc3 does.

llvm-gcc4 does not support the GCC indirect goto extension, but llvm-gcc3 does.

• "long double" is transformed by the front-end into "double". There is no support for floating point data types of any size other than 32 and 64 bits.
• Although many GCC extensions are supported, some are not. In particular, the following extensions are known to not be supported:
  1. Local Labels: Labels local to a block.
  2. Nested Functions: As in Algol and Pascal, lexical scoping of functions.
  3. Constructing Calls: Dispatching a call to another function.
  4. Thread-Local: Per-thread variables.
  5. Pragmas: Pragmas accepted by GCC.

  The following GCC extensions are partially supported. An ignored attribute means that the LLVM compiler ignores the presence of the attribute, but the code should still work. An unsupported attribute is one which is ignored by the LLVM compiler and will cause a different interpretation of the program.

  1. Variable Length: Arrays whose length is computed at run time.
     Supported, but allocated stack space is not freed until the function returns (noted above).
  2. Function Attributes: Declaring that functions have no side effects or that they can never return.
     Supported: alias, constructor, destructor, deprecated, fastcall, format, format_arg, non_null, noreturn, regparm section, stdcall, unused, used, visibility, warn_unused_result, weak
     Ignored: noinline, always_inline, pure, const, nothrow, malloc, no_instrument_function, cdecl
     Unsupported: All other target specific attributes
  3. Variable Attributes: Specifying attributes of variables.
     Supported: alias, cleanup, common, nocommon, deprecated, dllimport, dllexport, section, transparent_union, unused, used, weak
     Unsupported: aligned, mode, packed, shared, tls_model, vector_size, all target specific attributes.
  4. Type Attributes: Specifying attributes of types.
     Supported: transparent_union, unused, deprecated, may_alias
     Unsupported: aligned, packed, all target specific attributes.
  5. Other Builtins: Other built-in functions.
     We support all builtins which have a C language equivalent (e.g., __builtin_cos), __builtin_alloca, __builtin_types_compatible_p, __builtin_choose_expr, __builtin_constant_p, and __builtin_expect (currently ignored). We also support builtins for ISO C99 floating point comparison macros (e.g., __builtin_islessequal), __builtin_prefetch, __builtin_popcount[ll], __builtin_clz[ll], and __builtin_ctz[ll].

  The following extensions are known to be supported:

  1. Labels as Values: Getting pointers to labels and computed gotos.
  2. Statement Exprs: Putting statements and declarations inside expressions.
  3. Typeof: typeof: referring to the type of an expression.
  4. Lvalues: Using ?:, "," and casts in lvalues.
  5. Conditionals: Omitting the middle operand of a ?: expression.
  6. Long Long: Double-word integers.
  7. Complex: Data types for complex numbers.
  8. Hex Floats:Hexadecimal floating-point constants.
  9. Zero Length: Zero-length arrays.
  10. Empty Structures: Structures with no members.
  11. Variadic Macros: Macros with a variable number of arguments.
  12. Escaped Newlines: Slightly looser rules for escaped newlines.
  13. Extended Asm: Assembler instructions with C expressions as operands.
  14. Constraints: Constraints for asm operands.
  15. Asm Labels: Specifying the assembler name to use for a C symbol.
  16. Explicit Reg Vars: Defining variables residing in specified registers.
  17. Vector Extensions: Using vector instructions through built-in functions.
  18. Target Builtins: Built-in functions specific to particular targets.
  19. Subscripting: Any array can be subscripted, even if not an lvalue.
  20. Pointer Arith: Arithmetic on void-pointers and function pointers.
  21. Initializers: Non-constant initializers.
  22. Compound Literals: Compound literals give structures, unions, or arrays as values.
  23. Designated Inits: Labeling elements of initializers.
  24. Cast to Union: Casting to union type from any member of the union.
  25. Case Ranges: `case 1 ... 9' and such.
  26. Mixed Declarations: Mixing declarations and code.
  27. Function Prototypes: Prototype declarations and old-style definitions.
  28. C++ Comments: C++ comments are recognized.
  29. Dollar Signs: Dollar sign is allowed in identifiers.
  30. Character Escapes: \e stands for the character <ESC>.
  31. Alignment: Inquiring about the alignment of a type or variable.
  32. Inline: Defining inline functions (as fast as macros).
  33. Alternate Keywords:__const__, __asm__, etc., for header files.
  34. Incomplete Enums: enum foo;, with details to follow.
  35. Function Names: Printable strings which are the name of the current function.
  36. Return Address: Getting the return or frame address of a function.
  37. Unnamed Fields: Unnamed struct/union fields within structs/unions.
  38. 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).

For this release, the C++ front-end is considered to be fully tested and works for a number of non-trivial programs, including LLVM itself.

• llvm-gcc4 does not support C++ exception handling at all yet.
• Destructors for local objects are not always run when a longjmp is performed. In particular, destructors for objects in the longjmping function and in the setjmp receiver function may not be run. Objects in intervening stack frames will be destroyed, however (which is better than most compilers).
• The LLVM C++ front-end follows the Itanium C++ ABI. This document, which is not Itanium specific, specifies a standard for name mangling, class layout, v-table layout, RTTI formats, and other C++ representation issues. Because we use this API, code generated by the LLVM compilers should be binary compatible with machine code generated by other Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc). However, the exception handling mechanism used by llvm-gcc3 is very different from the model used in the Itanium ABI, so exceptions will not interact correctly.

A wide variety of additional information is available on the LLVM web page, including documentation and publications describing algorithms and components implemented in LLVM. The web page also contains versions of the API documentation which is up-to-date with the CVS 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.