diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 1b44ac553cb..038df8713ff 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -3,12 +3,12 @@ - LLVM 1.1 Release Notes + LLVM 1.2 Release Notes
- LLVM 1.1 Release Notes + LLVM 1.2 Release Notes
    @@ -42,10 +42,10 @@

    This document contains the release notes for the LLVM compiler -infrastructure, release 1.1. Here we describe the status of LLVM, including any +infrastructure, release 1.2. Here we describe the status of LLVM, including any known problems, and bug fixes from the previous release. The most up-to-date version of this document can be found on the LLVM 1.1 web site. If you are +href="http://llvm.cs.uiuc.edu/releases/1.2/">LLVM 1.2 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.

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

    -

    This is the second public release of the LLVM compiler infrastructure. This -release is primarily a bugfix release, dramatically improving the C/C++ -front-end, and improving support for C++ in the LLVM core. This release also -includes a few new features, such as a simple profiler, support for Mac OS/X, -better interoperability with external source bases, a new example language -front-end, and improvements in a few optimizations.

    +

    This is the third public release of the LLVM compiler infrastructure. OTHER +OVERVIEW STUFF HERE. +

    At this time, LLVM is known to correctly compile and run all non-unwinding C & C++ SPEC CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist @@ -100,58 +97,8 @@ This release implements the following new features:

      -
    1. A new -LLVM profiler, similar to gprof is available
      2. - -
    2. LLVM and the C/C++ front-end now compile on Mac OS/X! Mac OS/X users can -now explore the LLVM optimizer with the C backend and interpreter. Note that -LLVM requires GCC 3.3 on Mac OS/X.
      3. - -
    3. LLVM has been moved -into an 'llvm' C++ namespace, for easier integration with third-party -code. Note that due to lack of namespace support in GDB 5.x, you will probably -want to upgrade to GDB 6 or better to debug LLVM code.
      4. - -
    4. -The build system now copies Makefiles dynamically from the source tree to the -object tree as subdirectories are built. This means that: -
        -
      1. - New directories can be added to the source tree, and the build will - automatically pick them up (i.e. no need to re-run configure). -
        2. - -
      2. - You will need to build LLVM from the top of the object tree once to ensure - that all of the Makefiles are copied into the object tree subdirectories. -
        3. -
      -
      5. - -
    5. A front-end for "Stacker" (a simple Forth-like language) is now - included in the main LLVM tree. - Additionally, Reid Spencer, the author, contributed a document describing his experiences writing Stacker, and the language itself. This document is invaluable for others writing front-ends targetting LLVM.
      6. - -
    6. The configure script will now configure all projects placed in the -llvm/projects directory.
      7. - -
    7. The -tailcallelim pass can now introduce "accumulator" variables - to transform functions in many common cases that it could not before.
      8. - -
    8. The -licm pass can now sink instructions out the bottom of loops -in addition to being able to hoist them out the top.
      9. - -
    9. The -basicaa pass (the default alias analysis) has been upgraded -to be significantly more -precise.
      10. - -
    10. LLVM 1.1 implements a simple size optimization for LLVM bytecode files. - This means that the 1.1 files are smaller than 1.0, but that 1.0 won't - read 1.1 bytecode files.
      11. - -
    11. The gccld program produces a runner script that includes command-line options to load the necessary shared objects.
      12. +
    12. +
    @@ -161,17 +108,8 @@ In this release, the following missing features were implemented:
      -
    1. The interpreter does not support -invoke or unwind
      2. - -
    2. Interpreter does not support the -vaarg instruction
      3. - -
    3. llvm-nm cannot read archive -files
      4. - -
    4. Interpreter does not handle -setne constant expression
      5. +
    5. +
    @@ -183,37 +121,9 @@ fixed:
      -
    1. The C++ front-end now compiles functions to - use the linkonce linkage type - more, giving the optimizer more freedom.
      2. +
    2. -
    3. The C front-end now generates - type-safe code in several cases that it did not before, which prevented - some important optimizations.
      4. - -
    4. The LLVM build system has been taught to catch some common configuration - problems that caused it to get - horribly confused before.
      5. - -
    5. The LLVM header files are now - -Wold-style-cast clean.
      6. - -
    6. The LLVM bytecode reader has been sped up a lot (up to 4x in some -cases).
      7. - -
    7. In C++, methods and functions in anonymous namespaces now get internal linkage.
      8. - -
    8. Constant initializers now generate loops instead of potentially huge amounts of straight-line code.
      9. - -
    9. Code for running C++ destructors is now properly shared when possible. Before, the C++ front-end -generated N^2 amounts of duplicated cleanup code in some cases.
      10. - -
    10. The JIT used to generate code for - all functions pointed to by globals immediately, before the program - started execution, but now it waits until the first time they are called to - compile them. This dramatically speeds up short runs of large C++ programs, - which often have large numbers of functions pointed to by vtables.
      11. +
    @@ -225,70 +135,16 @@ In this release, the following bugs in the previous release were fixed:

    Bugs in the LLVM Core:

      -
    1. [inliner] Inlining invoke with PHI in unwind target is broken
      2. -
    2. [linker] linkonce globals should link successfully to external globals
      3. -
    3. [constmerge] Constant merging pass merges constants with external linkage
      4. -
    4. [scalarrepl] Scalar Replacement of aggregates is decimating structures it shouldn't be
      5. -
    5. [instcombine] Resolving invoke inserts cast after terminator
      6. -
    6. llvm-as crashes when labels are used in phi nodes
      7. -
    7. [build problem] Callgraph.cpp not pulled in from libipa.a
      8. -
    8. Variables in scope of output setjmp -calls should be volatile (Note that this does not effect correctness on -many platforms, such as X86).
      9. -
    9. [X86] Emission of global bool initializers broken
      10. -
    10. [gccld] The -r (relinking) option does not work correctly
      11. -
    11. [bcreader] Cannot read shift constant expressions from bytecode file
      12. -
    12. [lowersetjmp] Lowersetjmp pass breaks dominance properties!
      13. -
    13. SymbolTable::getUniqueName is very inefficient
      14. -
    14. bugpoint must not pass -R<directory> to Mach-O linker
      15. -
    15. [buildscripts] Building into objdir with .o in it fails
      16. -
    16. [setjmp/longjmp] Linking C programs which use setjmp/longjmp sometimes fail with references to the C++ runtime library!
      17. -
    17. AsmParser Misses Symbol Redefinition Error
      18. -
    18. gccld -Lfoo -lfoo fails to find ./foo/libfoo.a
      19. -
    19. [bcreader] Incorrect cast causes misread forward constant references
      20. -
    20. [adce] ADCE considers blocks without postdominators to be unreachable
      21. -
    21. [X86] div and rem constant exprs invalidate iterators!
      22. -
    22. [vmcore] Symbol table doesn't rename colliding variables during type resolution
      23. -
    23. Archive reader does not understand 4.4BSD/Mac OS X long filenames
      24. -
    24. [llvm-ar] Command line arguments have funny syntax
      25. +
    25. [licm] LICM promotes volatile memory locations to registers
      26. +

    Bugs in the C/C++ front-end:

      -
    1. C++ frontend can crash when compiling virtual base classes
      2. -
    2. C backend fails on constant cast expr to ptr-to-anonymous struct
      3. -
    3. #ident is not recognized by C frontend
      4. -
    4. C front-end miscompiles the builtin_expect intrinsic!
      5. -
    5. 1.0 precompiled libstdc++ does not include wchar_t support
      6. -
    6. llvmgcc asserts when compiling functions renamed with asm's
      7. -
    7. C frontend crashes on some programs with lots of types.
      8. -
    8. llvm-gcc crashes compiling global union initializer
      9. -
    9. C front-end crash on empty structure
      10. -
    10. CFrontend crashes when compiling C99 compound expressions
      11. -
    11. llvm-gcc infinite loops on "case MAXINT:"
      12. -
    12. [C++] Catch blocks make unparsable labels
      13. -
    13. [C++] Initializing array with constructable objects fail
      14. -
    14. llvm-gcc tries to add bools
      15. -
    15. [c++] C++ Frontend lays out superclasses like anonymous bitfields!
      16. -
    16. C front-end miscompiles unsigned enums whose LLVM types are signed
      17. -
    17. Casting a string constant to void crashes llvm-gcc
      18. -
    18. [llvmg++] Enum types are incorrectly shrunk to smaller than 'int' size
      19. -
    19. [llvmg++] Cannot use pointer to member to initialize global
      20. -
    20. [llvm-gcc] ?: operator as lvalue not implemented
      21. -
    21. [C/C++] Bogus warning about taking the address of 'register' variable
      22. -
    22. crash assigning into an array in a struct which contains a bitfield.
      23. -
    23. Oversized integer bitfields cause crash
      24. -
    24. [llvm-gcc] Bitfields & large array don't mix well
      25. -
    25. [llvm-gcc] Complex division is not supported
      26. -
    26. [llvm-gcc] Illegal union field reference
      27. -
    27. [llvmg++] Front-end attempts to return structure by value
      28. -
    28. [llvmg++] Pointer to member initializers not supported in constructors
      29. -
    29. [llvm-gcc] crash on union initialization
      30. -
    30. [llvm-g++] ?: expressions do not run correct number of destructors!
      31. -
    31. [llvm-gcc] Pointer & constant results in invalid shift
      32. -
    32. [llvmg++] call through array of pointers to member functions causes assertion
      33. +
    33. +
    @@ -302,7 +158,7 @@ many platforms, such as X86).

    LLVM has been extensively tested on Intel and AMD machines running Red -Hat Linux and has been tested on Sun UltraSPARC workstations running Solaris 8. +Hat Linux and FreeBSD. It has also been tested on Sun UltraSPARC workstations running Solaris 8. Additionally, LLVM works on Mac OS/X 10.3 and above, but only with the C backend or interpreter (no native backend for the PowerPC is available yet). @@ -369,9 +225,7 @@ more than 256 elements.

    -
    - Bugs -
    +
    Bugs