From: John Criswell Date: Mon, 29 Mar 2004 20:23:11 +0000 (+0000) Subject: Merged in RELEASE_12. X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=d179961d400f13d7c39b658d0682dc0a758c8f77;p=oota-llvm.git Merged in RELEASE_12. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@12532 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/CommandGuide/analyze.html b/docs/CommandGuide/analyze.html index cd66ce5e0da..ff61808f2b2 100644 --- a/docs/CommandGuide/analyze.html +++ b/docs/CommandGuide/analyze.html @@ -53,11 +53,6 @@ language. list of available analysis passes.

-

  • -dsa-track-integers -
    - Track integers as potential pointers. -

    -

  • -profile-info-file <filename>
    Specify the name of the file loaded by the -profile-loader option. diff --git a/docs/CommandGuide/bugpoint.html b/docs/CommandGuide/bugpoint.html index c6ac7abd10e..62e5787f86e 100644 --- a/docs/CommandGuide/bugpoint.html +++ b/docs/CommandGuide/bugpoint.html @@ -190,6 +190,16 @@ non-obvious ways. Here are some hints and tips:

    when attempting to reduce test programs. If you're trying to find a bug in one of these passes, bugpoint may crash.

    +

  • -enable-correct-eh-support
    + Make the -lowerinvoke pass insert expensive, but correct, exception + handling code.

    + +

  • -internalize-public-api-file <filename>
    + Preserve the symbols listed in the file filename.

    + +

  • -internalize-public-api-list <list>
    + Preserve the symbols listed in list.

    +

  • -help
    Print a summary of command line options.

    @@ -215,6 +225,9 @@ non-obvious ways. Here are some hints and tips:

    bugpoint will attempt to generate a reference output by compiling the program with the C backend and running it.

    +

  • -profile-info-file <filename>
    + Profile file loaded by -profile-loader.

    +

  • -run-{int,jit,llc,cbe}
    Whenever the test program is compiled, bugpoint should generate code for it using the specified code generator. These options allow diff --git a/docs/CommandGuide/opt.html b/docs/CommandGuide/opt.html index 4bf67a49c25..2e531a9202b 100644 --- a/docs/CommandGuide/opt.html +++ b/docs/CommandGuide/opt.html @@ -53,11 +53,6 @@ writes its output to the standard output. Specify the output filename.

    -

  • -dsa-track-integers -
    - Track integers as potential pointers. -

    -

  • -profile-info-file <filename>
    Specify the name of the file loaded by the -profile-loader option. diff --git a/docs/FAQ.html b/docs/FAQ.html index 87e6c13f356..74f0ea40f45 100644 --- a/docs/FAQ.html +++ b/docs/FAQ.html @@ -49,6 +49,8 @@
  • I've built LLVM and am testing it, but the tests freeze.
  • Why do test results differ when I perform different types of builds?
  • Compiling LLVM with GCC 3.3.2 fails, what should I do?
    • +
  • When I use the test suite, all of the C Backend tests fail. What is + wrong?
  • Using the GCC Front End @@ -341,6 +343,31 @@ build.

    affects projects other than LLVM. Try upgrading or downgrading your GCC.

    +
    +

    +When I use the test suite, all of the C Backend tests fail. What is +wrong? +

    +
    + +
    +

    +If you build LLVM and the C Backend tests fail in llvm/test/Programs, +then chances are good that the directory pointed to by the LLVM_LIB_SEARCH_PATH +environment variable does not contain the libcrtend.a library. +

    + +

    +To fix it, verify that LLVM_LIB_SEARCH_PATH points to the correct directory +and that libcrtend.a is inside. For pre-built LLVM GCC front ends, this +should be the absolute path to +cfrontend/<platform>/llvm-gcc/bytecode-libs. If you've +built your own LLVM GCC front end, then ensure that you've built and installed +the libraries in llvm/runtime and have LLVM_LIB_SEARCH_PATH pointing +to the LLVMGCCDIR/bytecode-libs subdirectory. +

    +
    +
    Using the GCC Front End diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 6490c0cf280..04cd6820124 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -183,10 +183,10 @@ software you will need.

  • Linux on x86 (Pentium and above) @@ -194,10 +194,10 @@ software you will need.

  • Solaris on SparcV9 (Ultrasparc) @@ -205,9 +205,9 @@ software you will need.

  • FreeBSD on x86 (Pentium and above)
  • LLVM now no longer depends on the boost library.
    • -
  • The X86 backend now generates substantially better native code, and is faster.
    • +
  • The X86 backend now generates substantially better native code and is faster.
  • The C backend has been turned moved from the "llvm-dis" tool to the "llc" tool. You can activate it with "llc -march=c foo.bc -o foo.c".
  • LLVM includes a new interprocedural optimization that marks global variables "constant" when they are provably never written to.
    • -
  • LLVM now includes a new interprocedural optimization that converts small "by reference" arguments to "by value" arguments, which is often improve the performance of C++ programs substantially.
    • +
  • LLVM now includes a new interprocedural optimization that converts small "by reference" arguments to "by value" arguments, which often improves the performance of C++ programs substantially.
  • Bugpoint can now do a better job reducing miscompilation problems by reducing programs down to a particular loop nest, instead of just the function being miscompiled.
    • @@ -145,7 +145,7 @@ In this release, the following missing features were implemented:
    1. Exception handling in the X86 & Sparc native code generators is now supported
      2. -
    2. The C/C++ front-end now support the GCC __builtin_return_address and __builtin_frame_address extensions. These are also supported by the X86 backend and by the C backend.
      3. +
    3. The C/C++ front-end now supports the GCC __builtin_return_address and __builtin_frame_address extensions. These are also supported by the X86 backend and by the C backend.
    4. [X86] Missing cast from ULong -> Double, cast FP -> bool and support for -9223372036854775808
    5. The C/C++ front-end now supports the "labels as values" GCC extension, often used to build "threaded interpreters".
      6. diff --git a/test/Makefile b/test/Makefile index ad9c6ecbd47..f52f5437958 100644 --- a/test/Makefile +++ b/test/Makefile @@ -34,6 +34,10 @@ ifeq ($(OS),SunOS) QMEXPECT:=$(LLVM_SRC_ROOT)/test/QMTest/expectations.sunos.qmr endif +ifeq ($(OS),Darwin) +QMEXPECT:=$(LLVM_SRC_ROOT)/test/QMTest/expectations.darwin.qmr +endif + # # This is configuration information used by the test suite. In QM Test, it's # called a 'context.'