OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

test.xml: Improve documentation on running a subset of tests.

Browse Source 
* doc/xml/manual/test.xml: Improve documentation on running a subset
	of tests.
	* doc/html/manual/test.html: Regenerate.

From-SVN: r221985
This commit is contained in:
Jonathan Wakely 2015-04-10 20:59:32 +01:00 committed by Jonathan Wakely
parent 54e915b362
commit cd80c79ce7
3 changed files with 38 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
libstdc++-v3/ChangeLog
View File

@ -1,3 +1,9 @@
2015-04-10 Jonathan Wakely <jwakely@redhat.com>
* doc/xml/manual/test.xml: Improve documentation on running a subset
of tests.
* doc/html/manual/test.html: Regenerate.
2015-04-10 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
* config/abi/post/powerpc-linux-gnu/baseline_symbols.txt: Update

18
libstdc++-v3/doc/html/manual/test.html
View File

@ -166,12 +166,20 @@ make check-target-libstdc++-v3 RUNTESTFLAGS="-v"
</p><pre class="programlisting">
make check-target-libstdc++-v3 RUNTESTFLAGS="-v -v"
</pre><p>
To run a subset of the library tests, you will need to generate
the <span class="emphasis"><em>testsuite_files</em></span> file by running
To run a subset of the library tests, you can either generate the
<span class="emphasis"><em>testsuite_files</em></span> file (described below) by running
<span class="command"><strong>make testsuite_files</strong></span> in the
<span class="emphasis"><em>libbuilddir/testsuite</em></span> directory, described
below. Edit the file to remove the tests you don't want and
then run the testsuite as normal.
<span class="emphasis"><em>libbuilddir/testsuite</em></span> directory, then edit the
file to remove the tests you don't want and then run the testsuite as
normal, or you can specify a testsuite and a subset of tests in the
RUNTESTFLAGS variable.
</p><p>
For example, to run only the tests for containers you could use:
</p><pre class="programlisting">
make check-target-libstdc++-v3 RUNTESTFLAGS="conformance.exp=23_containers/*"
</pre><p>
When combining this with other options in RUNTESTFLAGS the
<span class="emphasis"><em>testsuite.exp=testfiles</em></span> options must come first.
</p><p>
There are two ways to run on a simulator: set up DEJAGNU to point to a
specially crafted site.exp, or pass down --target_board flags.

24
libstdc++-v3/doc/xml/manual/test.xml
View File

@ -279,12 +279,26 @@ make check-target-libstdc++-v3 RUNTESTFLAGS="-v -v"
</programlisting>
<para>
To run a subset of the library tests, you will need to generate
the <emphasis>testsuite_files</emphasis> file by running
To run a subset of the library tests, you can either generate the
<emphasis>testsuite_files</emphasis> file (described below) by running
<command>make testsuite_files</command> in the
<emphasis>libbuilddir/testsuite</emphasis> directory, described
below. Edit the file to remove the tests you don't want and
then run the testsuite as normal.
<emphasis>libbuilddir/testsuite</emphasis> directory, then edit the
file to remove the tests you don't want and then run the testsuite as
normal, or you can specify a testsuite and a subset of tests in the
RUNTESTFLAGS variable.
</para>
<para>
For example, to run only the tests for containers you could use:
</para>
<programlisting>
make check-target-libstdc++-v3 RUNTESTFLAGS="conformance.exp=23_containers/*"
</programlisting>
<para>
When combining this with other options in RUNTESTFLAGS the
<emphasis>testsuite.exp=testfiles</emphasis> options must come first.
</para>
<para>