X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FTestingGuide.html;h=3be9279673d6764c95060f551bddfc40ae098d02;hb=6fc205fc446050a434e49e7cfcac89bb5d4435b1;hp=ced17745def3c64feeffecacd896a1b84c014c21;hpb=fc1a27b2a5d36f33585a2db1a7740913df24b893;p=oota-llvm.git diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html index ced17745def..3be9279673d 100644 --- a/docs/TestingGuide.html +++ b/docs/TestingGuide.html @@ -88,6 +88,12 @@ this route, you MUST specify all three components, and you need to only specify filenames themselves on the configure line. + +

Darwin (Mac OS X) developers can simplify the installation of Expect and tcl +by using fink. fink install expect will install both. Alternatively, +Darwinports users can use sudo port install expect to install Expect +and tcl.

+ @@ -112,13 +118,17 @@ or
 % gmake check
-

To run only a subdirectory of tests in llvm/test using DejaGNU (ie. Regression/Transforms). Just substitute the path to the subdirectory:

+ +

To run only a subdirectory of tests in llvm/test using DejaGNU (ie. +Regression/Transforms), just set the TESTSUITE variable to the path of the +subdirectory (relative to llvm/test):

 % gmake -C llvm/test TESTSUITE=Regression/Transforms
-

Note: If you are running the tests with objdir != subdir you must -have run the complete testsuite before you can specify a subdirectory.

+

Note: If you are running the tests with objdir != subdir, you +must have run the complete testsuite before you can specify a +subdirectory.

To run the comprehensive test suite (tests that compile and execute whole programs), run the llvm-test tests:

@@ -141,8 +151,8 @@ programs), run the llvm-test tests:

The LLVM test suite contains two major categories of tests: code fragments and whole programs. Code fragments are in the llvm module -under the directory under the llvm/test directory. The whole programs -test suite are in the llvm-test module under the main directory.

+under the llvm/test directory. The whole programs +test suite is in the llvm-test module under the main directory.

@@ -313,14 +323,14 @@ platforms support grep -C. that you might find useful when writing RUN lines.

Lastly, you can easily mark a test that is expected to fail on a -specific platform by using the XFAIL keyword. Xfail lines are +specific platform or with a specific version of llvmgcc by using the XFAIL keyword. Xfail lines are specified in the comments of the test program using XFAIL, followed by a colon, and one or more regular expressions (separated by -a comma) that will match against the target triplet for the -machine. You can use * to match all targets. Here is an example of an +a comma) that will match against the target triplet or llvmgcc version for the +machine. You can use * to match all targets. You can specify the major or full version (i.e. 3.4) for llvmgcc. Here is an example of an XFAIL line:

-; XFAIL: darwin,sun
+; XFAIL: darwin,sun,llvmgcc4
@@ -396,8 +406,8 @@ test suite creates temporary files during execution.

tests. By default, it will run all of these tests.

To run only the DejaGNU driven tests, run gmake at the -command line in llvm/tests. To run a specific directory of tests, use the -TESTSUITE variable. +command line in llvm/test. To run a specific directory of tests, use +the TESTSUITE variable.

For example, to run the Regression tests, type @@ -412,7 +422,7 @@ directory to run them.

  1. cd into the llvm/projects directory
  2. check out the llvm-test module with:
    - cvs -d :pserver:anon@llvm.cs.uiuc.edu:/var/cvs/llvm co -PR llvm-test
    + cvs -d :pserver:anon@llvm.org:/var/cvs/llvm co -PR llvm-test
    This will get the test suite into llvm/projects/llvm-test
  3. configure the test suite. You can do this one of two ways:
      @@ -422,7 +432,7 @@ directory to run them.

      properly configured.
    1. Use the configure script found in the llvm-test source directory:
      - $BUILD_SRC_DIR/configure --with-llvmsrc=$LLVM_SRC_ROOT --with-llvmobj=$LLVM_OBJ_ROOT + $LLVM_SRC_ROOT/projects/llvm-test/configure --with-llvmsrc=$LLVM_SRC_ROOT --with-llvmobj=$LLVM_OBJ_ROOT
  4. gmake
    5. @@ -450,7 +460,7 @@ others are features that we haven't added yet (or may never add). In DejaGNU, the result for such tests will be XFAIL (eXpected FAILure). In this way, you can tell the difference between an expected and unexpected failure.

    -

    The tests in llvm-test have no such feature as of this time. If the +

    The tests in llvm-test have no such feature at this time. If the test passes, only warnings and other miscellaneous output will be generated. If a test fails, a large <program> FAILED message will be displayed. This will help you separate benign warnings from actual test failures.

    @@ -464,7 +474,7 @@ will help you separate benign warnings from actual test failures.

    -The LLVM Nightly Testers +The LLVM Nightly Testers automatically check out an LLVM tree, build it, run the "nightly" program test (described above), run all of the feature and regression tests, and then delete the checked out tree. This tester is designed to ensure that @@ -488,7 +498,7 @@ The optimized x86 Linux nightly test is run from just such a script:

     #!/bin/bash
 BASE=/proj/work/llvm/nightlytest
-export CVSROOT=:pserver:anon@llvm.cs.uiuc.edu:/var/cvs/llvm
+export CVSROOT=:pserver:anon@llvm.org:/var/cvs/llvm
 export BUILDDIR=$BASE/build 
 export WEBDIR=$BASE/testresults 
 export LLVMGCCDIR=/proj/work/llvm/cfrontend/install
@@ -516,8 +526,8 @@ we'll link your page to the global tester page.  Thanks!
    
   Valid HTML 4.01!
 
-  John T. Criswell
    
-  The LLVM Compiler Infrastructure
    
+  John T. Criswell, Reid Spencer, and Tanya Lattner
    
+  The LLVM Compiler Infrastructure
    
   Last modified: $Date$