This patch add 'cd' command before 'make check-gcc' command
when run the testsuite on selected tests.
Richard and I agree it would be good for clarity and
emphasis to have the cd in the example as well, although
the text above the example was trying to restrict that to
objdir/gcc.
Tested on x86_64. OK for master?
Regards!
Hujp
---
gcc/doc/install.texi | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 5330bf3bb29..1560615bf3c 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2963,8 +2963,9 @@ on a simulator as described at
@uref{http://gcc.gnu.org/simtest-howto.html}.
@section How can you run the testsuite on selected tests?
In order to run sets of tests selectively, there are targets
-@samp{make check-gcc} and language specific @samp{make check-c},
-@samp{make check-c++}, @samp{make check-d} @samp{make check-fortran},
+@samp{make check-gcc}, @samp{make check-g++} and language specific
+@samp{make check-c},
+@samp{make check-c++}, @samp{make check-d}, @samp{make check-fortran},
@samp{make check-ada}, @samp{make check-objc}, @samp{make check-obj-c++},
@samp{make check-lto}
in the @file{gcc} subdirectory of the object directory. You can also
@@ -2975,14 +2976,14 @@ A more selective way to just run all @command{gcc}
execute tests in the
testsuite is to use
@smallexample
-make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
+cd @var{objdir}/gcc; make check-gcc RUNTESTFLAGS="execute.exp
@var{other-options}"
@end smallexample
Likewise, in order to run only the @command{g++} ``old-deja'' tests in
the testsuite with filenames matching @samp{9805*}, you would use
@smallexample
-make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
+cd @var{objdir}/gcc; make check-g++ RUNTESTFLAGS="old-deja.exp=9805*
@var{other-options}"
@end smallexample
The file-matching expression following @var{filename}@command{.exp=} is treated
@@ -2991,8 +2992,8 @@ may be passed, although any whitespace must either be
escaped or surrounded by
single quotes if multiple expressions are desired. For example,
@smallexample
-make check-g++ RUNTESTFLAGS="old-deja.exp=9805*\ virtual2.c
@var{other-options}"
-make check-g++ RUNTESTFLAGS="'old-deja.exp=9805* virtual2.c'
@var{other-options}"
+@dots{}"old-deja.exp=9805*\ virtual2.c @var{other-options}"
+@dots{}"'old-deja.exp=9805* virtual2.c' @var{other-options}"
@end smallexample
The @file{*.exp} files are located in the testsuite directories of the GCC
@@ -3010,7 +3011,7 @@ You can pass multiple options to the testsuite using the
work outside the makefiles. For example,
@smallexample
-make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
+cd @var{objdir}/gcc; make check-g++
RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
@end smallexample
will run the standard @command{g++} testsuites (``unix'' is the target name
@@ -3063,7 +3064,7 @@ make -j@var{N}
check-@var{testsuite}//@var{test-target}/@var{option1}/@var{optio
For example,
@smallexample
-make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
+cd @var{objdir}/gcc; make -j3
check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
@end smallexample
will run three concurrent ``make-gcc'' testsuites, eventually testing all
--
2.17.1
