From e84843b808a2ba1df8d84b24804386e554f7ac63 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Mon, 20 Oct 2003 19:05:03 +0000 Subject: [PATCH] Update release notes git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9296 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/ReleaseNotes.html | 31 ++++++++++--------------------- 1 file changed, 10 insertions(+), 21 deletions(-) diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 596d24aed94..8a0c2257c31 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -100,15 +100,10 @@ At link-time, the following optimizations are run:

  • Interprocedural dead code elimination (-globaldce)

    - -TODO: Works on: SPEC CPU 2000

    -TODO: Works on: Olden/Ptrdist benchmarks

    - -The What's New section should give a bulletted list of what is -included, perhaps a couple of lists (Stable, Beta).

    - -It would be useful to give a pointer to a list of the available passes (at least -for the standard compiler techniques).

    +At this time, LLVM is known to work properly with SPEC CPU 2000, 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. For these programs you must use the C backend.

    @@ -163,7 +158,8 @@ sections.

  • It is not possible to dlopen an LLVM bytecode file in the JIT.

    -

  • Linking in static archive files (.a files) is very slow. +
  • Linking in static archive files (.a files) is very slow (there is no symbol +table in the archive).

    Known problems with the C front-end

    Known problems with the Sparc back-end