X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FReleaseNotes.html;h=94e5c7b398a460c00bb237d53301cd7852a4235f;hb=2db49d797b86b7f3615bae17b2b016727778a6c4;hp=f271a6dd8d791b56579500674e4ab7e7954f572e;hpb=0e464a9170d08a4fb82920c77419ea6f64eb5804;p=oota-llvm.git diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index f271a6dd8d7..94e5c7b398a 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -4,20 +4,20 @@ - LLVM 2.7 Release Notes + LLVM 2.8 Release Notes -
LLVM 2.7 Release Notes
+
LLVM 2.8 Release Notes
+ width="136" height="136" alt="LLVM Dragon Logo">
  1. Introduction
  2. Sub-project Status Update
  3. -
  4. External Projects Using LLVM 2.7
  5. -
  6. What's New in LLVM 2.7?
  7. +
  8. External Projects Using LLVM 2.8
  9. +
  10. What's New in LLVM 2.8?
  11. Installation Instructions
  12. Portability and Supported Platforms
  13. Known Problems
  14. @@ -28,10 +28,10 @@

    Written by the LLVM Team

    -

    These are in-progress notes for the upcoming LLVM 2.7 +

    These are in-progress notes for the upcoming LLVM 2.8 release.
    You may prefer the -LLVM 2.6 +LLVM 2.7 Release Notes.

    @@ -43,7 +43,7 @@ Release Notes.

    This document contains the release notes for the LLVM Compiler -Infrastructure, release 2.7. Here we describe the status of LLVM, including +Infrastructure, release 2.8. Here we describe the status of LLVM, including major improvements from the previous release and significant known problems. All LLVM releases may be downloaded from the LLVM releases web site.

    @@ -51,8 +51,8 @@ href="http://llvm.org/releases/">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.

    +href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">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 @@ -67,32 +67,22 @@ Almost dead code. include/llvm/Analysis/LiveValues.h => Dan lib/Transforms/IPO/MergeFunctions.cpp => consider for 2.8. llvm/Analysis/PointerTracking.h => Edwin wants this, consider for 2.8. - ABCD, SCCVN, GEPSplitterPass + ABCD, GEPSplitterPass MSIL backend? + lib/Transforms/Utils/SSI.cpp -> ABCD depends on it. --> - @@ -103,7 +93,7 @@ Almost dead code.

    -The LLVM 2.7 distribution currently consists of code from the core LLVM +The LLVM 2.8 distribution currently consists of code from the core LLVM repository (which roughly includes the LLVM optimizers, code generators and supporting tools), the Clang repository and the llvm-gcc repository. In addition to this code, the LLVM Project includes other sub-projects that are in @@ -120,12 +110,49 @@ development. Here we include updates on these subprojects.

    -

    The Clang project is ...

    +

    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 and Objective-C on x86 (32- and 64-bit).

    In the LLVM 2.7 time-frame, the Clang team has made many improvements:

      -
    • ...
    • + +
    • C++ Support: Clang is now capable of self-hosting! While still +alpha-quality, Clang's C++ support has matured enough to build LLVM and Clang, +and C++ is now enabled by default. See the Clang C++ compatibility +page for common C++ migration issues.
    • + +
    • Objective-C: Clang now includes experimental support for an updated +Objective-C ABI on non-Darwin platforms. This includes support for non-fragile +instance variables and accelerated proxies, as well as greater potential for +future optimisations. The new ABI is used when compiling with the +-fobjc-nonfragile-abi and -fgnu-runtime options. Code compiled with these +options may be mixed with code compiled with GCC or clang using the old GNU ABI, +but requires the libobjc2 runtime from the GNUstep project.
    • + +
    • New warnings: Clang contains a number of new warnings, including +control-flow warnings (unreachable code, missing return statements in a +non-void function, etc.), sign-comparison warnings, and improved +format-string warnings.
    • + +
    • CIndex API and Python bindings: Clang now includes a C API as part of the +CIndex library. Although we may make some changes to the API in the future, it +is intended to be stable and has been designed for use by external projects. See +the Clang +doxygen CIndex +documentation for more details. The CIndex API also includes a preliminary +set of Python bindings.
    • + +
    • ARM Support: Clang now has ABI support for both the Darwin and Linux ARM +ABIs. Coupled with many improvements to the LLVM ARM backend, Clang is now +suitable for use as a beta quality ARM compiler.
    • +
    @@ -136,13 +163,18 @@ development. Here we include updates on these subprojects.
    -

    Previously announced in the 2.4, 2.5, and 2.6 LLVM releases, the Clang project also -includes an early stage static source code analysis tool for automatically finding bugs -in C and Objective-C programs. The tool performs checks to find -bugs that occur on a specific path within a program.

    - -

    In the LLVM 2.7 time-frame, the analyzer core has sprouted legs and...

    +

    The Clang Static Analyzer + project is an effort to use static source code analysis techniques to + automatically find bugs in C and Objective-C programs (and hopefully C++ in the + future!). The tool is very good at finding bugs that occur on specific + paths through code, such as on error conditions.

    + +

    In the LLVM 2.7 time-frame, the analyzer core has made several major and + minor improvements, including better support for tracking the fields of + structures, initial support (not enabled by default yet) for doing + interprocedural (cross-function) analysis, and new checks have been added. +

    @@ -159,13 +191,23 @@ implementation of the CLI) using LLVM for static and just-in-time compilation.

    -VMKit version ?? builds with LLVM 2.7 and you can find it on its -web page. The release includes -bug fixes, cleanup and new features. The major changes are:

    +With the release of LLVM 2.7, VMKit has shifted to a great framework for writing +virtual machines. VMKit now offers precise and efficient garbage collection with +multi-threading support, thanks to the MMTk memory management toolkit, as well +as just in time and ahead of time compilation with LLVM. The major changes in +VMKit 0.27 are:

      -
    • ...
    • +
    • Garbage collection: VMKit now uses the MMTk toolkit for garbage collectors. + The first collector to be ported is the MarkSweep collector, which is precise, + and drastically improves the performance of VMKit.
    • +
    • Line number information in the JVM: by using the debug metadata of LLVM, the + JVM now supports precise line number information, useful when printing a stack + trace.
    • +
    • Interface calls in the JVM: we implemented a variant of the Interface Method + Table technique for interface calls in the JVM. +
    @@ -189,39 +231,41 @@ libgcc routines).

    All of the code in the compiler-rt project is available under the standard LLVM -License, a "BSD-style" license.

    +License, a "BSD-style" license. New in LLVM 2.7: compiler_rt now +supports ARM targets.

    -KLEE: Symbolic Execution and Automatic Test Case Generator +DragonEgg: llvm-gcc ported to gcc-4.5

    -The new LLVM KLEE project is a symbolic -execution framework for programs in LLVM bitcode form. KLEE tries to -symbolically evaluate "all" paths through the application and records state -transitions that lead to fault states. This allows it to construct testcases -that lead to faults and can even be used to verify algorithms. For more -details, please see the OSDI 2008 paper about -KLEE.

    - -
    +DragonEgg is a port of llvm-gcc to +gcc-4.5. Unlike llvm-gcc, which makes many intrusive changes to the underlying +gcc-4.2 code, dragonegg in theory does not require any gcc-4.5 modifications +whatsoever (currently one small patch is needed). This is thanks to the new +gcc plugin architecture, which +makes it possible to modify the behaviour of gcc at runtime by loading a plugin, +which is nothing more than a dynamic library which conforms to the gcc plugin +interface. DragonEgg is a gcc plugin that causes the LLVM optimizers to be run +instead of the gcc optimizers, and the LLVM code generators instead of the gcc +code generators, just like llvm-gcc. To use it, you add +"-fplugin=path/dragonegg.so" to the gcc-4.5 command line, and gcc-4.5 magically +becomes llvm-gcc-4.5! +

    - -
    -DragonEgg: GCC-4.5 as an LLVM frontend -
    +

    +DragonEgg is still a work in progress. Currently C works very well, while C++, +Ada and Fortran work fairly well. All other languages either don't work at all, +or only work poorly. For the moment only the x86-32 and x86-64 targets are +supported, and only on linux and darwin (darwin needs an additional gcc patch). +

    -

    -The goal of DragonEgg is to make -gcc-4.5 act like llvm-gcc without requiring any gcc modifications whatsoever. -DragonEgg is a shared library (dragonegg.so) -that is loaded by gcc at runtime. It ... +DragonEgg is a new project which is seeing its first release with llvm-2.7.

    @@ -234,9 +278,27 @@ that is loaded by gcc at runtime. It ...

    -The LLVM Machine Code (MC) Toolkit project is ... +The LLVM Machine Code (aka MC) sub-project of LLVM 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. It is a sub-project of LLVM which provides it with a number of advantages +over other compilers that do not have tightly integrated assembly-level tools. +For a gentle introduction, please see the Intro to the +LLVM MC Project Blog Post.

    +

    2.7 includes major parts of the work required by the new MC Project. A few + targets have been refactored to support it, and work is underway to support a + native assembler in LLVM. This work is not complete in LLVM 2.7, but it has + made substantially more progress on LLVM mainline.

    + +

    One minor example of what MC can do is to transcode an AT&T syntax + X86 .s file into intel syntax. You can do this with something like:

    +
    +  llvm-mc foo.s -output-asm-variant=1 -o foo-intel.s
    +
    +
    @@ -253,53 +315,6 @@ The LLVM Machine Code (MC) Toolkit project is ... projects that have already been updated to work with LLVM 2.7.

    - - -
    -Rubinius -
    - -
    -Need update. - -

    - -
    - - -
    -MacRuby -
    - -
    - -

    -Need update. -

    - -
    - -
    Pure @@ -307,8 +322,6 @@ handling.-->

    -Need update. -

    -
    - +

    Pure versions 0.43 and later have been tested and are known to work with +LLVM 2.7 (and continue to work with older LLVM releases >= 2.5).

    - - - -
    -

    -Need update. - -

    @@ -351,13 +343,11 @@ fully featured as the original DMD compiler from DigitalMars.-->

    -Need update. -

    +

    @@ -367,28 +357,47 @@ reimplementation of an earlier project that is now based on LLVM.

    -Need update. - +compiler.

    -Need update. - +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 llvm-gcc/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.

    + +
    + + + + +
    +

    +SAFECode is a memory safe C +compiler built using LLVM. It takes standard, unannotated 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.

    @@ -399,18 +408,70 @@ code.-->

    -Need update. - +code.

    +

    Icedtea6 1.8 and later have been tested and are known to work with +LLVM 2.7 (and continue to work with older LLVM releases >= 2.6 as well). +

    +
    + + + +
    +

    +LLVM-Lua uses LLVM + to add JIT and static compiling support to the Lua VM. Lua +bytecode is analyzed to remove type checks, then LLVM is used to compile the +bytecode down to machine code. +

    +

    LLVM-Lua 1.2.0 have been tested and is known to work with LLVM 2.7. +

    +
    + + + + +
    +

    +MacRuby is an implementation of Ruby based on +core Mac OS technologies, sponsored by Apple Inc. It uses LLVM at runtime for +optimization passes, JIT compilation and exception handling. It also allows +static (ahead-of-time) compilation of Ruby code straight to machine code. +

    +

    The upcoming MacRuby 0.6 release works with LLVM 2.7. +

    +
    + + + + +
    +

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

    + +

    In addition to the existing C and native code generators, GHC now +supports an LLVM +code generator. GHC supports LLVM 2.7.

    + +
    @@ -428,6 +489,39 @@ in this section.
    + +
    +LLVM Community Changes +
    + +
    + +

    In addition to changes to the code, between LLVM 2.6 and 2.7, a number of +organization changes have happened: +

    + + +
    +
    Major New Features @@ -438,7 +532,40 @@ in this section.

    LLVM 2.7 includes several major new capabilities:

    @@ -453,7 +580,30 @@ in this section. expose new optimization opportunities:

    @@ -470,12 +620,51 @@ release includes a few major enhancements and additions to the optimizers:

    -

    Also, -anders-aa was removed

    - @@ -487,15 +676,20 @@ release includes a few major enhancements and additions to the optimizers:

    @@ -512,8 +706,49 @@ infrastructure, which allows us to implement more aggressive algorithms and make it run faster:

    @@ -527,31 +762,12 @@ it run faster:

    - - - - -
    -PIC16 Target Improvements -
    - -
    -

    New features of the PIC16 target include: -

    - - - -

    Things not yet supported:

    - -
    @@ -567,25 +783,31 @@ it run faster:

    - +
  15. The ARM backend now generates instructions in unified assembly syntax.
  16. - +
  17. llvm-gcc now has complete support for the ARM v7 NEON instruction set. This + support differs slightly from the GCC implementation. Please see the + + ARM Advanced SIMD (NEON) Intrinsics and Types in LLVM Blog Post for + helpful information if migrating code from GCC to LLVM-GCC.
  18. + +
  19. The ARM and Thumb code generators now use register scavenging for stack + object address materialization. This allows the use of R3 as a general + purpose register in Thumb1 code, as it was previous reserved for use in + stack address materialization. Secondly, sequential uses of the same + value will now re-use the materialized constant.
  20. - -
    -Other Target Specific Improvements -
    +
  21. The ARM backend now has good support for ARMv4 targets and has been tested + on StrongARM hardware. Previously, LLVM only supported ARMv4T and + newer chips.
  22. -
    -

    New features of other targets include: -

    +
  23. Atomic builtins are now supported for ARMv6 and ARMv7 (__sync_synchronize, + __sync_fetch_and_add, etc.).
  24. - +
    @@ -600,7 +822,34 @@ it run faster:

    @@ -615,7 +864,16 @@ it run faster:

    Other miscellaneous features include:

    @@ -633,46 +891,44 @@ on LLVM 2.6, this section lists some "gotchas" that you may run into upgrading from the previous release.

    +configure with --enable-libffi. + +
  25. Debug information uses a completely different representation, an LLVM 2.6 +.bc file should work with LLVM 2.7, but debug info won't come forward.
  26. +
  27. The LLVM 2.6 (and earlier) "malloc" and "free" instructions got removed, + along with LowerAllocations pass. Now you should just use a call to the + malloc and free functions in libc. These calls are optimized as well as + the old instructions were.
  28. +

    In addition, many APIs have changed in this release. Some of the major LLVM API changes are:

    @@ -693,7 +949,7 @@ to llvm/System/DataTypes.h.
  29. Intel and AMD machines (IA32, X86-64, AMD64, EMT-64) running Red Hat Linux, Fedora Core, FreeBSD and AuroraUX (and probably other unix-like systems).
  30. -
  31. PowerPC and X86-based Mac OS X systems, running 10.3 and above in 32-bit +
  32. PowerPC and X86-based Mac OS X systems, running 10.4 and above in 32-bit and 64-bit modes.
  33. Intel and AMD machines running on Win32 using MinGW libraries (native).
  34. Intel and AMD machines running on Win32 with the Cygwin libraries (limited @@ -722,13 +978,7 @@ listed by component. If you run into a problem, please check the LLVM bug database and submit a bug if there isn't already one.

    -