[www-patch] Testing C++ changes

[Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>]

Hi,

here's a more elaborate version than in

http://gcc.gnu.org/ml/gcc/2003-11/msg01203.html

of how to test changes to the C++ front end.
The credits for writing down the commands go to Giovanni Bajo,
I only did the XHTMLification.

The patch also changes the layout of the C section to match the
C++ paragraph.

Is this OK?

Regards,
Volker


Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.56
diff -u -r1.56 contribute.html
--- contribute.html	17 Nov 2003 15:37:22 -0000	1.56
+++ contribute.html	26 Nov 2003 00:30:36 -0000
@@ -87,18 +87,38 @@
 regression tests to ensure that your patch does not break anything
 else.</p>
 
+<h3>Which tests to perform</h3>
+
 <p>If your change is to code that is not in a front end, or is to the
 C front end, you must perform a complete build of GCC and the runtime
 libraries included with it, on at least one target.  You must
 bootstrap all languages, not just C.  You must also run all of the
 testsuites included with GCC and its runtime libraries.  For a normal
-native configuration, running <code>make bootstrap</code> followed by
-<code>make -k check</code> from the top level of the GCC tree
-(<strong>not</strong> the <code>gcc</code> subdirectory) will
-accomplish this.</p>
+native configuration, running</p>
+<blockquote><pre>
+make bootstrap
+make -k check
+</pre></blockquote>
+<p>from the top level of the GCC tree (<strong>not</strong> the
+<code>gcc</code> subdirectory) will accomplish this.</p>
+
+<p>If your change is to the C++ front end, you should rebuild the compiler,
+<code>libstdc++</code>, <code>libjava</code> and run the C++ testsuite.
+Given that you already did a complete C,C++,Java bootstrap from your build
+directory before, you can use the following:</p>
+<blockquote><pre>
+cd gcc
+make cc1plus    [.exe for cygwin]                      # build C++ compiler
+cd ..
+make clean-target-libstdc++-v3 all-target-libstdc++-v3 # rebuild libstdc++
+cd gcc/libjava
+make clean-nat all                                     # rebuild libjava
+cd ..
+make check-g++                                         # run C++ testsuite
+</pre></blockquote>
 
-<p>If your change is to a front end other than the C front end, or a
-runtime library other than <code>libgcc</code>, you need to verify
+<p>If your change is to a front end other than the C or C++ front end,
+or a runtime library other than <code>libgcc</code>, you need to verify
 only that the runtime library for that language still builds and the
 tests for that language have not regressed.  (Most languages have
 tests stored both in the <code>gcc</code> subdirectory, and in the