From: Chris Lattner Date: Sat, 6 Dec 2003 20:22:41 +0000 (+0000) Subject: Cleanup the release notes in preparation for the release. X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=a509996df2f7840a569e1f28894b55c14eebb8ad;p=oota-llvm.git Cleanup the release notes in preparation for the release. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@10294 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 24000707f9d..885a07774eb 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -71,22 +71,44 @@ href="http://llvm.cs.uiuc.edu/releases/">releases page.

This is the second public release of the LLVM compiler infrastructure. This -release implements the following new features:

+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 +features a few new features, such as a simple profiler, support for Mac OS/X, +and better interoperability with external source bases.

+ +

At this time, LLVM is known to correctly compile the SPEC CPU2000 benchmarks +(X86 only), the Olden benchmarks, and the Ptrdist benchmarks along with +many other programs. LLVM now also works with a fairly broad variety of +C++ programs, though it has still received much less testing than the C +front-end. +

+ +

+Note that the Sparc and X86 backends do not currently support exception throwing +or long jumping (including 253.perlbmk in SPEC). For these programs, you must +use the C backend. Support for unwinding will be added in a future release. +

+ + + +
+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 OSX! Mac OSX users can +
  3. 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 (note that LLVM requires GCC -3.3 on Mac OSX).
    4. +3.3 on Mac OS/X).
  4. LLVM has been moved into an 'llvm' C++ namespace, for easier integration with third-party -code. Note that due to a bug in GDB 5.x, to debug namespacified LLVM code, -you will need to upgrade to GDB 6.
    5. +code. Note that lack of namespace handling in GDB 5.x, you will probably want to +upgrade to GDB 6 or better to debug LLVM code.
  5. The build system now copies Makefiles dynamically from the source tree to the @@ -110,7 +132,11 @@ The configure script will now configure all projects placed in the
-

In this release, the following missing features were implemented:

+ + +
+In this release, the following missing features were implemented: +
  1. The interpreter does not support @@ -124,8 +150,12 @@ files
-

In this release, the following Quality of Implementation issues were -fixed:

+ + +
+In this release, the following Quality of Implementation issues were +fixed: +
    @@ -152,57 +182,69 @@ cases). generated N^2 amounts of duplicated cleanup code in some cases.
-

In this release, the following bugs in the previous release were fixed:

+ + +
+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. [linker] linkonce globals should link successfully to external globals
    3. -
  3. C++ frontend can crash when compiling virtual base classes
    4. -
  4. C backend fails on constant cast expr to ptr-to-anonymous struct
    5. -
  5. #ident is not recognized by C frontend
  6. [constmerge] Constant merging pass merges constants with external linkage
    7. -
  7. C front-end miscompiles the builtin_expect intrinsic!
  8. [scalarrepl] Scalar Replacement of aggregates is decimating structures it shouldn't be
    9. -
  9. 1.0 precompiled libstdc++ does not include wchar_t support
    10. -
  10. llvmgcc asserts when compiling functions renamed with asm's
    11. -
  11. C frontend crashes on some programs with lots of types.
  12. [instcombine] Resolving invoke inserts cast after terminator
  13. llvm-as crashes when labels are used in phi nodes
  14. [build problem] Callgraph.cpp not pulled in from libipa.a
  15. Variables in scope of output setjmp -calls should be volatile. Note that this does not effect correctness on -many platforms, such as X86.
    16. -
  16. llvm-gcc crashes compiling global union initializer
    17. -
  17. C front-end crash on empty structure
    18. -
  18. CFrontend crashes when compiling C99 compound expressions
    19. +calls should be volatile (Note that this does not effect correctness on +many platforms, such as X86).
  19. [X86] Emission of global bool initializers broken
    20. -
  20. llvm-gcc infinite loops on "case MAXINT:"
    21. -
  21. [C++] Catch blocks make unparsable labels
    22. -
  22. [C++] Initializing array with constructable objects fail
  23. [gccld] The -r (relinking) option does not work correctly
  24. [bcreader] Cannot read shift constant expressions from bytecode file
  25. [lowersetjmp] Lowersetjmp pass breaks dominance properties!
    26. -
  26. llvm-gcc tries to add bools
  27. SymbolTable::getUniqueName is very inefficient
  28. [buildscripts] Building into objdir with .o in it fails
  29. [setjmp/longjmp] Linking C programs which use setjmp/longjmp sometimes fail with references to the C++ runtime library!
    30. -
  30. [c++] C++ Frontend lays out superclasses like anonymous bitfields!
  31. AsmParser Misses Symbol Redefinition Error
  32. gccld -Lfoo -lfoo fails to find ./foo/libfoo.a
  33. [bcreader] Incorrect cast causes misread forward constant references
    34. -
  34. Casting a string constant to void crashes llvm-gcc
  35. [adce] ADCE considers blocks without postdominators to be unreachable
    36. -
  36. C front-end miscompiles unsigned enums whose LLVM types are signed
  37. [X86] div and rem constant exprs invalidate iterators!
    38. +
  38. [vmcore] Symbol table doesn't rename colliding variables during type resolution
    39. +
  39. bugpoint must not pass -R<directory> to Mach-O linker
    40. +
  40. gccld produces a runner script that includes command-line options to load the necessary shared objects
    41. +
+ + +

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. [llvmg++] Enum types are incorrectly shrunk to smaller than 'int' size
  19. [llvmg++] Cannot use pointer to member to initialize global
    20. -
  20. [vmcore] Symbol table doesn't rename colliding variables during type resolution
  21. [llvm-gcc] ?: operator as lvalue not implemented
  22. [C/C++] Bogus warning about taking the address of 'register' variable
    23. -
  23. bugpoint must not pass -R<directory> to Mach-O linker
  24. crash assigning into an array in a struct which contains a bitfield.
  25. Oversized integer bitfields cause crash
    26. -
  26. gccld produces a runner script that includes command-line options to load the necessary shared objects
  27. [llvm-gcc] Bitfields & large array don't mix well
  28. [llvm-gcc] Complex division is not supported
  29. [llvm-gcc] Illegal union field reference
    30. @@ -211,13 +253,8 @@ many platforms, such as X86.
  30. [llvm-gcc] crash on union initialization
  31. [llvm-g++] ?: expressions do not run correct number of destructors!
  32. [llvm-gcc] Pointer & constant results in invalid shift
    33. -

-

At this time, LLVM is known to work properly with SPEC CPU 2000 (X86 only), -the Olden benchmarks, and the Ptrdist benchmarks among many other programs. -Note however that the Sparc and X86 backends do not currently support exception -throwing or long jumping (including 253.perlbmk in SPEC). For these programs, -you must use the C backend.

+
@@ -577,10 +614,6 @@ Infinity. supported. This should not affect LLVM produced by the C or C++ frontends. -
  • The code produces by the C back-end has only been tested with the Sun CC, -GCC, and Intel compilers. It is possible that it will have to be adjusted to -support other C compilers.
    • -