From 6df9e2ca7049a7b79579a70b0178b7de4b5cd754 Mon Sep 17 00:00:00 2001 From: Misha Brukman Date: Wed, 12 May 2004 21:46:05 +0000 Subject: [PATCH] Break lines at 80 cols; eliminate extra space caused by a single

tag on a line by itself. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@13516 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/ReleaseNotes.html | 69 +++++++++++++++++++++--------------------- 1 file changed, 35 insertions(+), 34 deletions(-) diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 921b1df85a4..73068181840 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -69,21 +69,17 @@ href="http://llvm.cs.uiuc.edu/releases/">releases page.

-

-This is the fourth public release of the LLVM compiler infrastructure. This +

This is the fourth public release of the LLVM compiler infrastructure. This release primarily improves the performance of the code produced by all aspects of the LLVM compiler and adds some new features, though it does fix a few -bugs as well. -

+bugs as well.

-

-At this time, LLVM is known to correctly compile and run all C & C++ SPEC -CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist benchmarks. It has -also been used to compile many other programs. LLVM now also works with -a broad variety of C++ programs, though it has still received less testing than -the C front-end. -

+

At this time, LLVM is known to correctly compile and run all C & C++ +SPEC CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist benchmarks. It +has also been used to compile many other programs. LLVM now also works +with a broad variety of C++ programs, though it has still received less testing +than the C front-end.

@@ -134,7 +130,8 @@ issues were fixed:
  1. LLVM tools will happily spew bytecode onto your terminal
  2. -
  3. [llvmgcc] type names are not emitted for structure typedefs
  4. +
  5. [llvmgcc] type names are not emitted +for structure typedefs
@@ -143,8 +140,10 @@ In this release, the following build problems were fixed:
    -
  1. Minor configure bugs with -disable/enable-povray and -disable-spec
  2. -
  3. shell scripts output by gccld don't work if you change PATH
  4. +
  5. Minor configure bugs with +-disable/enable-povray and -disable-spec
  6. +
  7. shell scripts output by gccld don't +work if you change PATH
@@ -208,17 +207,21 @@ incorrectly updates dominator information breaks SSA form
  • [X86] JIT miscompiles unsigned short to floating point cast
  • -
  • [adce] Crash handling unreachable code that unwinds
  • -
  • [sparc] LLC can't emit 2 functions of -the same name, both having constant pools
  • -
  • [livevar] Live variables missed physical register use of aliased definition
  • +
  • [adce] Crash handling unreachable +code that unwinds
  • +
  • [sparc] LLC can't emit 2 functions +of the same name, both having constant pools
  • +
  • [livevar] Live variables missed +physical register use of aliased definition
  • Bugs in the C/C++ front-end:

      -
    1. [llvmgcc] Crash on use of undeclared enum type
    2. -
    3. [llvmgcc] Variable length array indexing miscompiled
    4. +
    5. [llvmgcc] Crash on use of undeclared +enum type
    6. +
    7. [llvmgcc] Variable length array +indexing miscompiled
    @@ -251,8 +254,10 @@ In this release, the following portability problems were fixed:
      -
    1. warnings compiling Stacker compiler on Mac OS X
    2. -
    3. Archive file reader doesn't understand abbreviated names in headers
    4. +
    5. warnings compiling Stacker compiler +on Mac OS X
    6. +
    7. Archive file reader doesn't +understand abbreviated names in headers
    @@ -278,13 +283,11 @@ there isn't already one.

    -

    -The following components of this LLVM release are either untested, known to be -broken or unreliable, or are in early development. These components should not -be relied on, and bugs should not be filed against them, but they may be useful -to some people. In particular, if you would like to work on one of these -components, please contact us on the llvmdev list. -

    +

    The following components of this LLVM release are either untested, known to +be broken or unreliable, or are in early development. These components should +not be relied on, and bugs should not be filed against them, but they may be +useful to some people. In particular, if you would like to work on one of these +components, please contact us on the llvmdev list.