Lines Matching full:testsuite
227 Necessary to run the GCC testsuite; see the section on testing for
983 testsuite on the stage-1 compiler for the specified languages
1745 Finally, you can run the testsuite (which may take a long time):
1749 ends and runtime libraries. While running the testsuite, DejaGnu might
1755 testsuite on a simulator as described at
1758 6.1 How can you run the testsuite on selected tests?
1767 testsuite is to use
1772 testsuite with filenames matching `9805*', you would use
1776 The `*.exp' files are located in the testsuite directories of the GCC
1785 You can pass multiple options to the testsuite using the
1793 for a standard native testsuite situation), passing `-O3
1803 group.) The following will run each testsuite eight times using the
1830 make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/...
1845 `TARGET/libjava/testsuite' directory in the build tree.
1849 the Mauve tree within the libjava testsuite at
1850 `libjava/testsuite/libjava.mauve/mauve', or by specifying the location
1856 The result of running the testsuite are various `*.sum' and `*.log'
1857 files in the testsuite subdirectories. The `*.log' files contain a
1872 * ERROR: the testsuite detected an error
1874 * WARNING: the testsuite detected a possible problem
1892 to the testsuite summary and should contain any special remarks you
1894 testsuite result block or the subject line, as these messages may be
2320 latest FSF binutils is known to improve overall testsuite results; and,
3240 Sun bug 4927647 sometimes causes random spurious testsuite failures
3243 which is used only by the GCC testsuite driver. When the bug causes
3244 the `expect' program to miss anticipated output, extra testsuite
4181 * Testsuite: Testing. (line 6)
