From 6bc80edc986a7afe2389deac4f18e8c1b976b66c Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Mon, 29 Jun 2009 16:41:45 +0000 Subject: gdb * README: Mention parallel check. gdb/testsuite * dg-extract-results.sh: New file. * Makefile.in (FORCE_PARALLEL): New variable. (CHECK_TARGET): New conditional variable. (check): Use CHECK_TARGET. (DO_RUNTEST): New variable. (check-single): New target. (TEST_DIRS): New variable. (TEST_TARGETS): Likewise. (check-parallel): New target. (check-gdb.%): New pattern. (BASE1_FILES): New variable. (BASE2_FILES): Likewise. (check-gdb.base%): New pattern. (%/.dir): New pattern. * configure: Rebuild. * aclocal.m4 (AM_CONDITIONAL): New defun. * configure.ac: Check whether user is using GNU make. (GMAKE): New conditional. --- gdb/README | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'gdb/README') diff --git a/gdb/README b/gdb/README index 7116227..57f600a 100644 --- a/gdb/README +++ b/gdb/README @@ -642,6 +642,20 @@ or make site.exp (builds the site specific file) runtest -tool gdb GDB=../gdb (or GDB= as appropriate) +When using a `make'-based method, you can use the Makefile variable +`RUNTESTFLAGS' to pass flags to `runtest', e.g.: + + make RUNTESTFLAGS=--directory=gdb.cp check + +If you use GNU make, you can use its `-j' option to run the testsuite +in parallel. This can greatly reduce the amount of time it takes for +the testsuite to run. In this case, if you set `RUNTESTFLAGS' then, +by default, the tests will be run serially even under `-j'. You can +override this and force a parallel run by setting the `make' variable +`FORCE_PARALLEL' to any non-empty value. Note that the parallel `make +check' assumes that you want to run the entire testsuite, so it is not +compatible with some dejagnu options, like `--directory'. + The last method gives you slightly more control in case of problems with building one or more test executables or if you are using the testsuite `standalone', without it being part of the GDB source tree. -- cgit v1.1