diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index e3390108305..d75a6f3d2c9 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -44,14 +44,14 @@

This document contains the release notes for the LLVM compiler infrastructure, release 1.4. Here we describe the status of LLVM, including any -known problems and bug fixes from the previous release. The most up-to-date +known problems and improvements from the previous release. The most up-to-date version of this document can be found on the LLVM 1.4 web site. If you are not reading this on the LLVM web pages, you should probably go there because this document may be updated after the release.

-

For more information about LLVM, including information about potentially more -current releases, please check out the main +

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.

@@ -73,9 +73,18 @@ href="http://llvm.cs.uiuc.edu/releases/">releases page.

This is the fifth public release of the LLVM compiler infrastructure.

-

At this time, LLVM is known to correctly compile and run all C & C++ -SPEC CPU95 & 2000 benchmarks, the Olden benchmarks, and the Ptrdist -benchmarks, and many other C and C++ programs.

+

At this time, LLVM is known to correctly compile and a broad range of +C and C++ programs, including the SPEC CPU95 & 2000 suite. This release +includes several major enhancements to the LLVM system, including a new +PowerPC JIT, enhancements to the C/C++ front-end to provide source line number +information in LLVM, a new compiler +driver, and several other enhancements listed below. It also includes +bug fixes for those problems found since the 1.3 release.

+ +

Note that this release seperates the LLVM Program Testsuite out of the +main LLVM distribution into a seperate CVS repository and tarball. This +reduces the size of the main LLVM distribution. Also note that LLVM now +builds tools into llvm/Debug/bin by default instead of llvm/tools/Debug.

@@ -86,71 +95,69 @@ benchmarks, and many other C and C++ programs.

    -
  1. LLVM now includes a JIT for the PowerPC target.
    2. -
  2. LLVM now optimizes global variables significantly more than it did - before. +
  3. LLVM now includes a Just-In-Time compiler for the PowerPC target.
    4. +
  4. llvmgcc and llvmg++ now emit source line number information when '-g' is + passed in. This information can be used with llvm-db or other tools and + passes.
    5. +
  5. The test/Programs hierarchy has + been moved out of the main LLVM tree into a separate CVS repository and + tarball. This shrinks the distribution size of LLVM itself significantly.
    6. +
  6. LLVM now optimizes global variables more aggressively than it did + before.
  7. LLVM now includes the new 'undef' value and unreachable instruction, which give the optimizer more information about the behavior of the program.
    8. -
  8. llvmgcc and llvmg++ now emit source line number information when '-g' is - passed in. This information can be used with llvm-db or other tools and - passes. -
    9. -
  9. The test/Programs hierarchy has - been moved out of the main LLVM tree into a separate CVS repository and - tarball. This shrinks the distribution size of LLVM itself significantly. -
  10. Bytecode compression with bzip2 has been implemented. All bytecode files generated by LLVM will now be compressed by default. Compression can be disabled with the -disable-compression option to the tools that can generate bytecode files.
    11. -
  11. A generic compiler driver and - an associated generic linker have - been implemented. The compiler driver is generic because it can be configured +
  12. A generic compiler driver + (llvmc) and + an associated generic linker + (llvm-ld) have been added. The compiler driver is generic because it can be + configured to pre-process, translate, optimize, assemble, and link code from any source - language. This aids compiler writers because all that is needed is a - source-to-bytecode or source-to-assembly translator and a configuration file. - The linker is generic because it allows dynamically loadable optimization - modules to be executed for link-time optimization. Language specific - link-time optimization modules can be created and executed automatically. + language with an LLVM front-end. This makes it easier for compiler writers + to hide the multiple steps required to compile a program (compiling, + optimizing, linking runtime libraries, etc) in one simple command.
  13. The dependent libraries feature has been implemented. This allows front end compilers to indicate in the bytecode which libraries the bytecode needs to be linked with. Both the C/C++ front end and Stacker support generating the required libraries. The - Linker now supports using this information to ensure required libaries are + linker now supports using this information to ensure required libaries are linked into the module. This minimizes the need to use the -l option when using llvmc
    14. -
  14. The LLVM makefiles have been improved to build LLVM faster (2x) and - includes new targets (like dist-check, uninstall). One important change is - associated with PR456. The - libraries and tools will now be built into $builddir/Debug/{bin,lib} - instead of $builddir/tools/Debug and $builddir/lib/Debug. - Similarly for Release and Profile builds. +
  15. The LLVM makefiles have been improved to build LLVM much faster and + includes new targets (like dist-check, uninstall). One important user-visible + change is that libraries and tools will now be built into + $builddir/Debug/{bin,lib} + instead of $builddir/tools/Debug and $builddir/lib/Debug + (Similarly for Release and Profile builds).
  16. The LLVM source code is much more compatible with Microsoft Visual C++, including the JIT and runtime-code generation, though the entire system may not work with it.
    17. -
  17. The target-to-JIT interfaces are +
  18. The JIT-Target interfaces are now much simpler and more powerful.
    19. +
  19. LLVM now provides llvm-ar and llvm-ranlib tools for working with archives + of LLVM bytecode files.
  20. zlib and libpng are no longer included in the main LLVM tarball.
    21. -
  21. The LLVM code generator now generates asm writers for the target from - an abstract target description, instead of requiring them to be hand - written.
    22. +
  22. The LLVM code generator now automatically generates assembly code writers + from an abstract target descriptions, eliminating the need to write + assembly printers manually.
  23. LLVM regression and feature tests can now be run with DejaGNU.
  24. llvmgcc and llvmg++ now emit source-level line number information, making it possible to map from LLVM code back to source. This is currently used by llvm-db.
    25. -
  25. Floating point intensive programs on X86 systems run much faster - with the LLC code generator and JIT than in 1.3.
@@ -187,14 +194,12 @@ issues were fixed:
    -
  1. - [core/asmparser] ConstantFP::isValueValidForType Broken +
  2. The linker no longer emits many + useless warnings when linking C++ programs.
    3. -
  3. [llvmg++] Tons of warnings - are spewed when linking to libstdc++ -
    4. -
  4. include/{Support,Config} -> - include/llvm/{Support,Config} +
  5. The LLVM #include namespace + has been made consistent. Files in llvm/include/{Support,Config} + are now located in llvm/include/llvm/{Support,Config}.
  6. The names of the libraries generated by compiling LLVM source have been changed to ensure they do not conflict with other packages upon installation. @@ -202,23 +207,13 @@ issues were fixed: the library libasmparser.a in 1.3 has become libLLVMAsmParser.a in release 1.4.
    7. -
  7. [llvmg++] C++ frontend is expanding - lots of unused inline functions
    8. -
+
  • The C++ frontend no longer expands and emits all inline functions, even if they + are unused. It now properly tracks which functions are needed and + only compiles those.
    • -
    - - -
    -In this release, the following build problems were fixed: -
    - -
    -
      -
    1. [autoconf] further standardizing - autoconf usage. Various improvements in the configure.ac script were - made as well as the makefile system. -
      2. +
    2. Many improvements in the autoconf + and makefile systems have been implemented.
    @@ -230,9 +225,12 @@ improvements:
      -
    1. Ugly code generated for - std::min/std::max -
      2. +
    2. The optimizer produces more + efficient code for std::min/std::max and other similar functions.
      3. +
    3. The X86 backend generates substantially faster code for floating point + intensive programs.
      4. +
    4. The PowerPC backend generates more efficient code in many common + scenarios.
    @@ -247,10 +245,6 @@ were fixed:

    Bugs fixed in the LLVM Core:

      -
    1. [Linker] gccld does not link - objects/archives in order specified on the command line
      2. -
    2. [X86] llc output for functions - w/certain names tickles GNU 'as' bugs
    3. [licm] LICM invalidates alias analysis info and uses broken information (optimizer crash)
    4. [asmwriter] Asmwriter is really @@ -259,6 +253,8 @@ were fixed: completely broken in LLVM 1.3
    5. [bcwriter] Empty compaction tables defined
      6. +
    6. [X86] llc output for functions + w/certain names tickles GNU 'as' bugs
    7. [cbackend] Static globals are prototyped as 'extern'
    @@ -274,7 +270,7 @@ were fixed: bitfield which does not increase struct size
  • [llvmgcc] llvmgcc emits invalid constant exprs
    • -
  • [llvmg++] Crash in initializing +
  • [llvmg++] Crash initializing array with constructors in hard EH situations
  • [llvm-gcc] Inline function redefinitions error due to 'asm' function rename
    • @@ -309,8 +305,9 @@ were fixed:
  • Intel and AMD machines running Red Hat Linux and FreeBSD (and probably other unix-like systems).
  • Sun UltraSPARC workstations running Solaris 8.
    • -
  • Intel and AMD machines running on Win32 with the Cygwin libraries.
    • -
  • PowerPC-based Mac OS X boxes, running 10.2 and above.
    • +
  • Intel and AMD machines running on Win32 with the Cygwin libraries (limited + support is available for native builds with Visual C++).
    • +
  • PowerPC-based Mac OS X systems, running 10.2 and above.

    • The core LLVM infrastructure uses @@ -319,6 +316,7 @@ 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.

    + @@ -360,11 +359,11 @@ useful to some people. In particular, if you would like to work on one of these components, please contact us on the llvmdev list.

    @@ -385,22 +384,10 @@ components, please contact us on the llvmdev list.

    such, execution of a threaded program could cause these data structures to be corrupted. -
  • Linking in static archive files (.a files) is slow by default because - there is no symbol table in the archive. To remedy this, run - llvm-ranlib on the - archive to add an LLVM symbol table. -
    • -
  • The gccld program does not link - objects/archives in the order specified on the command line. -
  • The lower-invoke pass does not mark values live across a setjmp as volatile. This missing feature only affects targets whose setjmp/longjmp libraries do not save and restore the entire register file.
    • -
  • [bytecode] Assertion on V1 - Bytecode Files. This bug won't be fixed because V1 bytecode had its own - problems, no one is using V1 bytecode any more, and the fix is non-trivial. -
    • @@ -426,9 +413,6 @@ components, please contact us on the llvmdev list.

  • Initialization of global union variables can only be done with the largest union member.
    • -
  • [llvm-gcc] Error when an implicitly -external function is re-declared as static
    • - @@ -581,10 +565,9 @@ lists, please let us know (also including whether or not they work).

    -

    For this release, the C++ front-end is considered to be fully functional but -has not been tested as thoroughly as the C front-end. It has been tested and -works for a number of non-trivial programs, but there may be lurking bugs. -Please report any bugs or problems.

    +

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

    @@ -696,10 +679,6 @@ 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. -
  • Initializers for global variables -cannot include special floating point numbers like Not-A-Number or -Infinity.
    • -
  • Zero arg vararg functions are not supported. This should not affect LLVM produced by the C or C++ frontends.