test.html: Add multilib RUNTESTFLAGS example.

2004-03-01  Benjamin Kosnik  <bkoz@redhat.com>

	* docs/html/test.html: Add multilib RUNTESTFLAGS example.

	* docs/html/18_support/howto.html: Add bit about writing to
	stderr, mostly by Zack.

From-SVN: r78709

libstdc++-v3/ChangeLog

+2004-03-01  Benjamin Kosnik  <bkoz@redhat.com>
+
+	* docs/html/test.html: Add multilib RUNTESTFLAGS example.
+
+	* docs/html/18_support/howto.html: Add bit about writing to
+	stderr, mostly by Zack.
+	
 2004-03-01  Paolo Carlini  <pcarlini@suse.de>
 
 	* include/bits/locale_facets.tcc (money_get<>::_M_extract,

libstdc++-v3/docs/html/18_support/howto.html

@@ -284,6 +284,13 @@
       <a href="../faq/index.html">to the FAQ</a>.
    </p>
 
+<p>
+   This function will attempt to write to stderr.  If your application
+    closes stderr or redirects it to an inappropriate location,
+    <code>__verbose_terminate_handler</code> will behave in an
+    unspecified manner.
+</p>
+
 <hr />
 <h2><a name="5">Dynamic memory management</a></h2>
    <p>There are six flavors each of <code>new</code> and

libstdc++-v3/docs/html/test.html

@@ -477,11 +477,11 @@ or
 make check-target-libstdc++-v3 RUNTESTFLAGS="-v -v"
 </pre>
 
+
 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.
 
 Example flags to pass down for various embedded builds are as follows:
-
 <pre>
 --target=powerpc-eabism (libgloss/sim)
 make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=powerpc-sim"
@@ -492,7 +492,14 @@ make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=calmrisc32-sid"
 --target=xscale-elf (newlib/sim)
 make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=arm-sim"
 </pre>
-   
+
+<p> Also, here is an example of how to run the libstdc++ testsuite for a
+multilibed build directory with different ABI settings:
+</p>
+<pre>
+make check-target-libstdc++-v3 RUNTESTFLAGS='--target_board \"unix{-mabi=32,,-mabi=64}\"'
+</pre>
+ 
   <p> To run a subset of the library tests, simply edit the generated
   file, <em>testsuite_files </em>, to include only the files that are
   desired instead of all available test cases.