This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Testing C++ changes
On Wed, 19 Nov 2003, Mark Mitchell wrote:
> I think we really ought to be doing everything we can to prevent
> bootstrap breakage.
>
> So, I think we should require that you rebuild the Java library when you
> change the C++ front end -- if you are using a platform where GCJ builds
> at all.
Okay.
On Wed, 19 Nov 2003, Tom Tromey wrote:
> In sum I'm not too concerned about running the libjava test suite for
> every C++ change. If we start seeing too many failures from not doing
> this, we can always change the policy to adapt.
Trying to summarize -- I'm just the documentation guy here, who'll
implement whatever you decide ;-) -- how about the patch below?
Gerald
Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.56
diff -u -3 -p -r1.56 contribute.html
--- contribute.html 17 Nov 2003 15:37:22 -0000 1.56
+++ contribute.html 22 Nov 2003 08:23:17 -0000
@@ -87,6 +87,8 @@ tests and add them to GCC's testsuite.
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
@@ -97,14 +99,15 @@ native configuration, running <code>make
(<strong>not</strong> the <code>gcc</code> subdirectory) will
accomplish this.</p>
-<p>If your change is to a front end other than the C front end, or a
+<p>If your change is to a front end other than C or C++, 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
-directory for the runtime library.) You need not bootstrap, or test
-other languages, since there is no way you could have affected
-them.</p>
+directory for the runtime library.)</p>
+
+<p>If your change is to the C++ front end, you need to perform the
+tests above for libstdc++ and build (but not test) libjava.</p>
<p>Since the Ada front end is written in Ada, if you change it you
must perform a complete bootstrap; however, running other language