From: Chris Lattner Date: Thu, 1 Apr 2004 00:41:31 +0000 (+0000) Subject: Clear out all of the changes. Reset version numbers to 1.3 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=2974b5b9bb8594e25454b6890681273bbf9bdd09;p=oota-llvm.git Clear out all of the changes. Reset version numbers to 1.3 add note about select git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@12584 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 7e7b2d6298c..9ae492a1e4f 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -3,13 +3,11 @@ - LLVM 1.2 Release Notes + LLVM 1.3 Release Notes -
- LLVM 1.2 Release Notes -
+
LLVM 1.3 Release Notes
  1. Introduction
  2. @@ -18,7 +16,8 @@
  3. Installation Instructions
  4. Known Problems
@@ -179,9 +117,7 @@ In this release, the following build problems were fixed:
    -
  1. [build] Makefiles break if C frontend target string has unexpected value
  2. -
  3. [build] hard-wired assumption that shared-library extension is ".so"
  4. -
  5. make tools-only doesn't make lib/Support
  6. +
@@ -190,12 +126,7 @@ In this release, the following build problems were fixed:
    -
  1. [loopsimplify] Many pointless phi nodes are created
  2. -
  3. [x86] wierd stack/frame pointer manipulation
  4. - -
  5. The X86 backend now generate fchs to negate floating point numbers, -compiles memcpy() into the rep movs instruction, and makes much better -use of powerful addressing modes and instructions.
  6. +
@@ -207,31 +138,7 @@ use of powerful addressing modes and instructions.

Bugs in the LLVM Core:

    -
  1. [licm] LICM promotes volatile memory -locations to registers
  2. -
  3. [licm] Memory read after free causes -infrequent crash
  4. -
  5. [indvars] Induction variable -canonicalization always makes 32-bit indvars
  6. -
  7. [constantmerge] Merging globals can -cause use of invalid pointers!
  8. -
  9. [bcreader] Bytecode reader misreads 'long -9223372036854775808'!
  10. -
  11. Tail duplication does not update SSA form correctly.
  12. -
  13. VMCore mishandles double -0.0
  14. -
  15. [X86] X86 backend code generates -0.0 as +0.0
  16. -
  17. [loopsimplify] Loopsimplify incorrectly updates dominator information
  18. -
  19. [pruneeh] -pruneeh pass removes invoke instructions it shouldn't
  20. -
  21. [sparc] Boolean constants are emitted as true and false
  22. -
  23. [interpreter] va_list values silently corrupted by function calls
  24. -
  25. Tablegen aborts on errors
  26. -
  27. [inliner] Error inlining intrinsic calls into invoke instructions
  28. -
  29. Linking weak and strong global variables is dependent on link order
  30. -
  31. Variables used to define non-printable FP constants are externally visible
  32. -
  33. CBE gives linkonce functions wrong linkage semantics
  34. -
  35. [JIT] Programs cannot resolve the fstat function
  36. -
  37. [indvars] Induction variable analysis violates LLVM invariants
  38. -
  39. [execution engines] Unhandled cast constant expression
  40. -
  41. [Sparc] Code generator asserts on alloca of zero size type
  42. +
@@ -239,17 +146,7 @@ cause use of invalid pointers!

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

    -
  1. Need weak linkage on memory -management functions in libc runtime to allow them to be overriden
  2. -
  3. [llvm-gcc] asserts when an extern inline function is redefined
  4. -
  5. [llvmg++] Dynamically initialized constants cannot be marked 'constant'
  6. -
  7. [llvmgcc] floating-point unary minus is incorrect for +0.0
  8. -
  9. [llvm-gcc] miscompilation of 'X = Y = Z' with aggregate values
  10. -
  11. [llvmgcc] Invalid code created for complex division operation
  12. -
  13. [llvmgcc] Incorrect code generation for pointer subtraction
  14. -
  15. [llvmg++] Crash assigning pointers-to-members with casted types
  16. -
  17. [llvm-g++] Cleanups and gotos don't mix properly
  18. -
  19. [llvmgcc] Crash on auto register variable with specific register specified
  20. +