Lines Matching full:testsuite
253 Necessary to run the GCC testsuite; see the section on testing for
1038 testsuite on the stage-1 compiler for the specified languages
1918 Finally, you can run the testsuite (which may take a long time):
1922 ends and runtime libraries. While running the testsuite, DejaGnu might
1928 testsuite on a simulator as described at
1931 6.1 How can you run the testsuite on selected tests?
1940 testsuite is to use
1945 testsuite with filenames matching `9805*', you would use
1949 The `*.exp' files are located in the testsuite directories of the GCC
1958 You can pass multiple options to the testsuite using the
1966 for a standard native testsuite situation), passing `-O3
1976 group.) The following will run each testsuite eight times using the
2003 make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/...
2018 `TARGET/libjava/testsuite' directory in the build tree.
2022 the Mauve tree within the libjava testsuite at
2023 `libjava/testsuite/libjava.mauve/mauve', or by specifying the location
2029 The result of running the testsuite are various `*.sum' and `*.log'
2030 files in the testsuite subdirectories. The `*.log' files contain a
2045 * ERROR: the testsuite detected an error
2047 * WARNING: the testsuite detected a possible problem
2065 to the testsuite summary and should contain any special remarks you
2067 testsuite result block or the subject line, as these messages may be
2457 latest FSF binutils is known to improve overall testsuite results; and,
3224 Sun bug 4927647 sometimes causes random spurious testsuite failures
3227 which is used only by the GCC testsuite driver. When the bug causes
3228 the `expect' program to miss anticipated output, extra testsuite
4200 * Testsuite: Testing. (line 6)
