This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFA: update gdb internals doc with parallel make check

>>>>> "Eli" == Eli Zaretskii <> writes:

Eli> The text is okay, of course, but I have a few markup comments:
Eli>  . Please use @option for command-line options
Eli>  . Please use @env for environment variables
Eli>  . Please use @kbd for commands typed by the user, such as "make
Eli>    check" in this case
Eli> Okay with those taken care of.

Here is what I'm committing.


2009-07-09  Tom Tromey  <>

	* gdbint.texinfo (Testsuite): Document parallel make check.

Index: doc/gdbint.texinfo
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.308
diff -u -r1.308 gdbint.texinfo
--- doc/gdbint.texinfo	10 Jul 2009 18:48:40 -0000	1.308
+++ doc/gdbint.texinfo	10 Jul 2009 19:37:02 -0000
@@ -7519,6 +7519,16 @@
 where @var{tests} is a list of test script file names, separated by
+If you use GNU make, you can use its @option{-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
+@code{RUNTESTFLAGS} then, by default, the tests will be run serially
+even under @option{-j}.  You can override this and force a parallel run
+by setting the @code{make} variable @code{FORCE_PARALLEL} to any
+non-empty value.  Note that the parallel @kbd{make check} assumes
+that you want to run the entire testsuite, so it is not compatible
+with some dejagnu options, like @option{--directory}.
 The ideal test run consists of expected passes only; however, reality
 conspires to keep us from this ideal.  Unexpected failures indicate
 real problems, whether in @value{GDBN} or in the testsuite.  Expected

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]