Table Of Contents

Previous topic

Debugging GCC

Next topic

How to improve the location of a gcc diagnostic

This Page

Working with the testsuite

Running just one test (or just a few)

1) Find the pertinent Tcl script that runs the test: a .exp script in the same directory, or one of the ancestors directories. The significant part is the filename.

For example, for test case gcc/testsuite/gcc.dg/pragma-diag-1.c, it’s gcc/testsuite/gcc.dg/dg.exp, where the filename is dg.exp.

2) Figure out the appropriate “make” target, normally based on the source language for the test. For the above example, it’s check-gcc.

3) Run make in your BUILDDIR/gcc, passing in a suitable value for RUNTESTFLAGS based on the filename found in step 1 above. For this case, giving it a couple of -v flags for verbosity (so that we can see the command-line of the compiler invocation) it would be:

$ make -jN && make check-gcc RUNTESTFLAGS="-v -v dg.exp=pragma-diag-1.c"

for some N; I like the make && make check-FOO construction to ensure that the compiler is rebuilt before running the tests.

You can also use wildcards e.g.:

make -j64 && make check-gcc RUNTESTFLAGS="-v -v dg.exp=pragma-diag-*.c"

(and can use -jN for some N on the make check-FOO invocation if there are a lot of tests; I tend not to use it for a small number of tests, to avoid interleaving of output in the logs).

“test for excess errors”

If a DejaGnu test is failing with “test for excess errors” you can go into gcc/testsuite/lib/prune.exp and uncomment this line within proc prune_gcc_output:

#send_user "After:$text\n"


send_user "After:$text\n"

This will print any messages that weren’t pruned by dg- directives.