From: Jonathan Wakely Date: Mon, 17 Dec 2007 21:37:26 +0000 (+0000) Subject: test.html: Fix paths and notes on running subset of tests. X-Git-Tag: releases/gcc-4.3.0~920 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=0d9f441aea99a5ddfb8d7592bf5e41b19114aa45;p=thirdparty%2Fgcc.git test.html: Fix paths and notes on running subset of tests. 2007-12-17 Jonathan Wakely * docs/html/test.html: Fix paths and notes on running subset of tests. * docs/html/ext/parallel_mode.html: Fix markup typos. * docs/html/ext/pb_ds/index.html: Likewise. From-SVN: r131019 --- diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index e6b0343844d0..3fc2fd27abae 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,9 @@ +2007-12-17 Jonathan Wakely + + * docs/html/test.html: Fix paths and notes on running subset of tests. + * docs/html/ext/parallel_mode.html: Fix markup typos. + * docs/html/ext/pb_ds/index.html: Likewise. + 2007-12-17 Benjamin Kosnik * testsuite/22_locale/global_templates/ diff --git a/libstdc++-v3/docs/html/ext/parallel_mode.html b/libstdc++-v3/docs/html/ext/parallel_mode.html index 2e4f6624f8de..7ca8dbe937cc 100644 --- a/libstdc++-v3/docs/html/ext/parallel_mode.html +++ b/libstdc++-v3/docs/html/ext/parallel_mode.html @@ -425,7 +425,7 @@ For each algorithm, a minimum problem size can be stated, usually using the variable __gnu_parallel::Settings::[algorithm]_minimal_n. Please see -<settings.h> for details.

+<settings.h> for details.

@@ -434,7 +434,7 @@ Please see

All parallel algorithms are intended to have signatures that are equivalent to the ISO C++ algorithms replaced. For instance, the std::adjacent_find function is declared as: - +

 namespace std
 {
@@ -444,8 +444,10 @@ namespace std
 }
+

Which means that there should be something equivalent for the parallel version. Indeed, this is the case: +

 namespace std
@@ -495,7 +497,7 @@ of threads available, etc., and are denoted by the use of the enum
 
 
 Putting all this together, the general view of overloads for the
 parallel algorithms look like this:
-

+

- More examples can be found in the libstdc++/testsuite/*/*.cc files. + More examples can be found in the libstdc++-v3/testsuite/*/*.cc files.

@@ -452,7 +452,7 @@ up in the normal.exp file. 
 make check

in the libbuilddir directory.

or

- 
 make check-target-libstdc++
+ 
 make check-target-libstdc++-v3

in the gccbuilddir directory.

@@ -472,19 +472,20 @@ specific argument to the variable RUNTESTFLAGS, as below. 

-make check-target-libstdc++ RUNTESTFLAGS="-v"
+make check-target-libstdc++-v3 RUNTESTFLAGS="-v"
or 
-make check-target-libstdc++ RUNTESTFLAGS="-v -v"
+make check-target-libstdc++-v3 RUNTESTFLAGS="-v -v"
-

To run a subset of the library tests, try using a command like the -following from the libbuilddir/testsuite directory: +

+To run a subset of the library tests, you will need to generate the +testsuite_files file by running make testsuite_files +in the libbuilddir/testsuite directory, described below. +Edit the file to remove the tests you don't want and then run the +testsuite as normal.

-
-runtest --tool libstdc++ normal.exp="`find $srcdir/17_intro -name *.cc`"
-

@@ -494,20 +495,20 @@ specially crafted site.exp, or pass down --target_board flags. Example flags to pass down for various embedded builds are as follows: 

 --target=powerpc-eabism (libgloss/sim)
-make check-target-libstdc++ RUNTESTFLAGS="--target_board=powerpc-sim"
+make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=powerpc-sim"
 
 --target=calmrisc32 (libgloss/sid)
-make check-target-libstdc++ RUNTESTFLAGS="--target_board=calmrisc32-sid"
+make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=calmrisc32-sid"
 
 --target=xscale-elf (newlib/sim)
-make check-target-libstdc++ RUNTESTFLAGS="--target_board=arm-sim"
+make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=arm-sim"

Also, here is an example of how to run the libstdc++ testsuite for a multilibed build directory with different ABI settings: 

-make check-target-libstdc++ RUNTESTFLAGS='--target_board \"unix{-mabi=32,,-mabi=64}\"'
+make check-target-libstdc++-v3 RUNTESTFLAGS='--target_board \"unix{-mabi=32,,-mabi=64}\"'

@@ -518,9 +519,11 @@ you must also ensure that the directory containing the shared version of libstdc++ is in your LD_LIBRARY_PATH, or equivalent. If your GCC source tree is at /path/to/gcc, then you can run the tests as follows: +

-runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++/testsuite
+runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++-v3/testsuite
+

The testsuite will create a number of files in the directory in which you run this command,. Some of those files might use the same name as files created by other testsuites (like the ones for GCC and G++), so @@ -610,7 +613,7 @@ directory.

Running debug-mode tests

To run the libstdc++ test suite under the debug mode, - edit libstdc++/scripts/testsuite_flags to add the + edit libstdc++-v3/scripts/testsuite_flags to add the compile-time flag -D_GLIBCXX_DEBUG to the result printed by the --build-cxx option. Additionally, add the -D_GLIBCXX_DEBUG_PEDANTIC flag to turn on pedantic