Lines Matching full:testsuite
230 Necessary to run the GCC testsuite; see the section on testing for
1613 Finally, you can run the testsuite (which may take a long time):
1617 ends and runtime libraries. While running the testsuite, DejaGnu might
1622 6.1 How can you run the testsuite on selected tests?
1631 testsuite is to use
1636 testsuite with filenames matching `9805*', you would use
1640 The `*.exp' files are located in the testsuite directories of the GCC
1649 You can pass multiple options to the testsuite using the
1657 for a standard native testsuite situation), passing `-O3
1667 group.) The following will run each testsuite eight times using the
1694 make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/...
1709 `TARGET/libjava/testsuite' directory in the build tree.
1713 the Mauve tree within the libjava testsuite at
1714 `libjava/testsuite/libjava.mauve/mauve', or by specifying the location
1717 Jacks is a free testsuite that tests Java compiler front ends. This
1719 within the libjava testsuite at `libjava/testsuite/libjava.jacks/jacks'.
1724 The result of running the testsuite are various `*.sum' and `*.log'
1725 files in the testsuite subdirectories. The `*.log' files contain a
1740 * ERROR: the testsuite detected an error
1742 * WARNING: the testsuite detected a possible problem
1760 to the testsuite summary and should contain any special remarks you
1762 testsuite result block or the subject line, as these messages may be
2202 latest FSF binutils is known to improve overall testsuite results; and,
3085 Sun bug 4927647 sometimes causes random spurious testsuite failures
3088 which is used only by the GCC testsuite
3089 the `expect' program to miss anticipated output, extra testsuite
4021 * Testsuite: Testing. (line 6)
