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
1925 Finally, you can run the testsuite (which may take a long time):
1929 ends and runtime libraries. While running the testsuite, DejaGnu might
1935 testsuite on a simulator as described at
1938 6.1 How can you run the testsuite on selected tests?
1947 testsuite is to use
1952 testsuite with filenames matching `9805*', you would use
1956 The `*.exp' files are located in the testsuite directories of the GCC
1965 You can pass multiple options to the testsuite using the
1973 for a standard native testsuite situation), passing `-O3
1983 group.) The following will run each testsuite eight times using the
2010 make -jN check-TESTSUITE//TEST-TARGET/OPTION1/OPTION2/...
2025 `TARGET/libjava/testsuite' directory in the build tree.
2029 the Mauve tree within the libjava testsuite at
2030 `libjava/testsuite/libjava.mauve/mauve', or by specifying the location
2036 The result of running the testsuite are various `*.sum' and `*.log'
2037 files in the testsuite subdirectories. The `*.log' files contain a
2052 * ERROR: the testsuite detected an error
2054 * WARNING: the testsuite detected a possible problem
2072 to the testsuite summary and should contain any special remarks you
2074 testsuite result block or the subject line, as these messages may be
2462 latest FSF binutils is known to improve overall testsuite results; and,
3229 Sun bug 4927647 sometimes causes random spurious testsuite failures
3232 which is used only by the GCC testsuite driver. When the bug causes
3233 the `expect' program to miss anticipated output, extra testsuite
4205 * Testsuite: Testing. (line 6)
