X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FReleaseNotes.html;h=56dd66a21aa53860577177cb78dd5c89a3456dc3;hb=8cb8245cf117fc4a4f0a6549d9a773a12895550c;hp=f1538e071e4035312b52b1c93291c519c81bc64b;hpb=c4e6b373299cb9d6aa3b43c26ff7a80bca7e116c;p=oota-llvm.git diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index f1538e071e4..56dd66a21aa 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -13,6 +13,7 @@
  1. Introduction
    2. +
  2. Major Changes and Sub-project Status
  3. What's New?
  4. Installation Instructions
  5. Portability and Supported Platforms
    6. @@ -55,7 +56,7 @@ current one. To see the release notes for a specific releases, please see the
    - What's New? + Major Changes and Sub-project Status
    @@ -79,68 +80,185 @@ It includes a large number of features and refinements from LLVM 2.2.

    -

    LLVM 2.2 was the last LLVM release to support llvm-gcc 4.0 and llvm-upgrade. -llvm-gcc 4.0 has been replaced with llvm-gcc 4.2. llvm-upgrade 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.

    +

    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.

    LLVM API Changes:

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

    +
    -

    LLVM 2.3 includes several major new capabilities:

    + +
    +vmkit +
    - @@ -351,8 +511,8 @@ faster:

    @@ -370,8 +530,9 @@ faster:

    @@ -456,13 +617,19 @@ href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list.

    all inline assembly that uses the X86 floating point stack. It supports the 'f' and 't' constraints, but not 'u'. -
  6. The X86 backend generates inefficient floating point code when configured to - generate code for systems that don't have SSE2.
    7. +
  7. The X86 backend generates inefficient floating point code when configured + to generate code for systems that don't have SSE2.
  8. 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 in FP stackifier + bugs due to lack of support for the + 'u' inline assembly constraint and X87 floating point inline assembly.
    9. +
  9. The X86-64 backend does not yet support position-independent code (PIC) + generation on Linux targets.
    10. +
  10. 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.
    11. @@ -494,7 +661,8 @@ processors, thumb programs can crash or produce wrong results (PR1388).
  11. Compilation for ARM Linux OABI (old ABI) is supported, but not fully tested.
    12. -
  12. There is a bug in QEMU-ARM (<= 0.9.0) which causes it to incorrectly execute +
  13. There is a bug in QEMU-ARM (<= 0.9.0) which causes it to incorrectly + execute programs compiled with LLVM. Please use more recent versions of QEMU.
    14. @@ -537,25 +705,9 @@ appropriate nops inserted to ensure restartability.
    @@ -584,9 +736,6 @@ programs. Known problems with the llvm-gcc C front-end - -
    Bugs
    -

    llvm-gcc does not currently support Link-Time @@ -651,11 +800,12 @@ crashing if an exception is raised. Workaround: do not use -E. or finish at a non-byte offset in a record. Workaround: do not pack records or use representation clauses that result in a field of a non-discrete type starting or finishing in the middle of a byte. -

  14. The lli interpreter considers 'main' -as generated by the Ada binder to be invalid. -Workaround: hand edit the file to use pointers for argv and envp rather than -integers.
    15. -
  15. The -fstack-check option is ignored.
    16. +
  16. The lli interpreter considers +'main' as generated by the Ada binder to be invalid. +Workaround: hand edit the file to use pointers for argv and +envp rather than integers.
    17. +
  17. The -fstack-check option is +ignored.