This patch check the command 'make check-g++' to 'make check-c++' in install.texi since there is no 'make check-g++' target in the object directory. It also adds some description in the above text, to clarity and emphasis the difference of the 'make check-<LANGUAGE>' targets in between object directory and the gcc subdirectory.
The earlier patch discussion is as follows: https://gcc.gnu.org/pipermail/gcc-patches/2020-August/552761.html https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553307.html Ok for master? Regards! Hujp --- gcc/doc/install.texi | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 5330bf3bb29..0a6a3271757 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -2964,10 +2964,13 @@ on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}. 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-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 +in both the object directory and the @file{gcc} subdirectory of the +object directory. Note these targets in the object directory will do +both the language tests and the related library tests while in the @file{gcc} +subdirectory of the object directory will do only language tests. You can also just run @samp{make check} in a subdirectory of the object directory. @@ -2978,11 +2981,11 @@ testsuite is to use make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}" @end smallexample -Likewise, in order to run only the @command{g++} ``old-deja'' tests in +Likewise, in order to run only the @command{c++} ``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}" +make check-c++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}" @end smallexample The file-matching expression following @var{filename}@command{.exp=} is treated @@ -2991,8 +2994,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,10 +3013,10 @@ 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" +@dots{}"--target_board=unix/-O3/-fmerge-constants" @end smallexample -will run the standard @command{g++} testsuites (``unix'' is the target name +will run the standard @command{c++} testsuites (``unix'' is the target name for a standard native testsuite situation), passing @samp{-O3 -fmerge-constants} to the compiler on every test, i.e., slashes separate options. -- 2.17.1