From f3e5bc695efab58771a8aa922f5078ba521f3a98 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Mon, 14 May 2007 06:56:09 +0000 Subject: [PATCH] Add a skeleton for future contents git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@37028 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/ReleaseNotes.html | 142 +++++++++++++++++++++-------------------- 1 file changed, 74 insertions(+), 68 deletions(-) diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 7f9f22f313c..c8a9fabf579 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -89,12 +89,40 @@ release series, like we did within the 1.x series. New Features in LLVM 2.0 + +
Major Changes
+
+

blah +

+ + + +
+ + + +
llvm-gcc +Improvements
+
+

New features include: +

+ + + +
+
Optimizer Improvements
-

The mid-level optimizer is now faster and produces better code in many cases. - Significant changes include:

+

New features include: +

-The LLVM Target-Independent code generator now supports more target features and -optimizes many cases more aggressively. New features include: +New features include:

+ +
Target-Specific +Improvements
+ +
+ +

New features include: +

+ + + +
+ +
Other Improvements
@@ -248,44 +291,34 @@ implement ordered FP comparisons.
- Known problems with the SPARC back-end + Known problems with the ARM back-end
    -
  • The SPARC backend only supports the 32-bit SPARC ABI (-m32), it does not - support the 64-bit SPARC ABI (-m64).
    • +
  • The Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6 +processors, any thumb program compiled with LLVM crashes or produces wrong +results. (PR1388)
    • +
  • Compilation for ARM Linux OABI (old ABI) is supported, but not fully tested. +
    • +
  • QEMU-ARM (<= 0.9.0) wrongly executes programs compiled with LLVM. A non-affected QEMU version must be used or this + +patch must be applied on QEMU.
- Known problems with the C back-end + Known problems with the SPARC back-end
    - -
  • The C back-end produces code that violates the ANSI C Type-Based Alias -Analysis rules. As such, special options may be necessary to compile the code -(for example, GCC requires the -fno-strict-aliasing option). This -problem probably cannot be fixed.
    • - -
  • Zero arg vararg functions are not -supported. This should not affect LLVM produced by the C or C++ -frontends.
    • - -
  • The C backend does not correctly implement the llvm.stacksave or -llvm.stackrestore -intrinsics. This means that some code compiled by it can run out of stack -space if they depend on these (e.g. C99 varargs).
    • - -
  • The C backend does not support inline - assembly code.
    • +
  • The SPARC backend only supports the 32-bit SPARC ABI (-m32), it does not + support the 64-bit SPARC ABI (-m64).
@@ -338,36 +371,18 @@ programs.
- Known problems with the ARM back-end + Known problems with the C back-end
    -
  • The Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6 -processors, any thumb program compiled with LLVM crashes or produces wrong -results. (PR1388)
    • -
  • Compilation for ARM Linux OABI (old ABI) is supported, but not fully tested. -
    • -
  • QEMU-ARM (<= 0.9.0) wrongly executes programs compiled with LLVM. A non-affected QEMU version must be used or this - -patch must be applied on QEMU.
    • +
  • The C backend does not support inline + assembly code.
- -
- Known problems with the LLVM Core -
- -
- -
    -
  • In the JIT, dlsym() on a symbol compiled by the JIT will not - work.
    • -
-
@@ -379,16 +394,12 @@ patch must be applied on QEMU.
-

- -

llvm-gcc4 is far more stable and produces better code than llvm-gcc3, but -does not currently support Link-Time -Optimization or C++ Exception Handling, -which llvm-gcc3 does.

- -

llvm-gcc4 does not support the GCC indirect -goto extension, but llvm-gcc3 does.

+

llvm-gcc4 does not currently support Link-Time +Optimization on most platforms "out-of-the-box". Please inquire on the +llvmdev mailing list if you are interested.

+

FIXME: the list of supported stuff below needs to be updated. We do support +tls now, what else??

@@ -531,20 +542,15 @@ lists, please let us know (also including whether or not they work).

-

For this release, the C++ front-end is considered to be fully +

The C++ front-end is considered to be fully tested and works for a number of non-trivial programs, including LLVM -itself.

- -
+itself, Qt, Mozilla, etc.

- -
- Notes -
- -
    -
  • llvm-gcc4 does not support C++ exception handling at all yet.
    • +
  • llvm-gcc4 only has partial support for C++ +Exception Handling, and it is not enabled by default.
    • + +
-- 2.34.1