From 47eff2be9a6ee25b4f21a58131c69719eeab78dc Mon Sep 17 00:00:00 2001 From: Duncan Sands Date: Sun, 8 Jun 2008 19:38:43 +0000 Subject: [PATCH] Fix spelling. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@52094 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/ReleaseNotes.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 82ba0c74b7e..015564a54d2 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -128,7 +128,7 @@ dispatching them to different tools.
  • Flexible (and extensible) rules for defining different tools.
  • The different intermediate steps performed by tools are represented as edges in the abstract graph.
    • -
  • The 'language' for driver behaviour definition is tablegen and thus +
  • The 'language' for driver behavior definition is tablegen and thus it's relatively easy to add new features.
  • The definition of driver is transformed into set of C++ classes, thus no runtime interpretation is needed.
    • @@ -228,7 +228,7 @@ for (i = LB; i < NUB; ++i)
  • LLVM includes a new memcpy optimization pass which optimizes out dead memcpy calls, unneeded copies of aggregates, and handles the return slot optimization. The LLVM optimizer now notices long sequences of -consequtive stores and merges them into memcpys where profitable.
    • +consecutive stores and merges them into memcpys where profitable.
  • Alignment detection for vector memory references and for memcpy and memset is now more aggressive.
    • @@ -247,7 +247,7 @@ deletion pass, which is safe for infinite loops. included at -O1 in llvm-gcc. It was also extended to include more optimizations and several corner case bugs are fixed. -
  • LLVM now includes a simple 'Jump Threading' pass, which attemps to simplify +
  • LLVM now includes a simple 'Jump Threading' pass, which attempts to simplify the conditional branches with information about predecessor blocks. This simplifies the control flow graph. This pass is pretty basic at this point, but catches some important cases and provides a foundation to build off @@ -306,7 +306,7 @@ faster:

    area of passing and returning structures by value. llvm-gcc compiled code now interoperates very well on X86-64 systems with other compilers.
    • -
  • Support for Win64 was added. This includes codegeneration itself, JIT +
  • Support for Win64 was added. This includes code generation itself, JIT support and necessary changes to llvm-gcc.
  • The LLVM X86 backend now supports the support SSE 4.1 instruction set, and @@ -459,7 +459,7 @@ href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list.

    'u'.
  • The X86 backend generates inefficient floating point code when configured to generate code for systems that don't have SSE2.
    • -
  • Win64 codegeneration wasn't widely tested. Everything should work, but we +
  • Win64 code generation wasn't widely tested. Everything should work, but we expect small issues to happen. Also, llvm-gcc cannot build mingw64 runtime currently due to several @@ -554,7 +554,7 @@ compilers.
    • output with code built with other compilers, particularly for floating-point programs. -
  • Defining vararg functions is not supported (but calling them is ok).
    • +
  • Defining vararg functions is not supported (but calling them is OK).
  • The Itanium backend has bitrotted somewhat.