Testing instructions for 2.95

Wed Dec 13 09:56:00 GMT 2000

On Wed, 13 Dec 2000, Bernd Schmidt wrote:
> I've added the following two files to the gcc-2.95.2 directory in the html
> documentation.  I haven't added links yet; I'd prefer if someone with more
> html skills than me could have a glance at it first and tell me if it looks
> OK.

Looks OK!

I made a few markup changes (<code> instead of <tt>, <a href> instead of
<A HREF>, <br> instead of <nl>, adding <p></p> and </li>) and committed
the following patch; nothing really substantial.

(As I'm on a leave at a University in Italy until December 22nd, I won't
have much time to devote to GCC these days, but I'll try to help where
possible...)

Gerald


Index: testing.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-2.95/testing.html,v
retrieving revision 1.1
retrieving revision 1.3
diff -u -3 -p -r1.1 -r1.3

--- testing.html	2000/12/13 16:20:46	1.1
+++ testing.html	2000/12/13 17:53:06	1.3
@@ -7,49 +7,60 @@
 <body>
 <h1 align="center">Testing GCC 2.95 with the current testsuite</h1>

-For the upcoming gcc-2.95.3 release, we need to perform tests on as many
+<p>For the upcoming GCC 2.95.3 release, we need to perform tests on as many
 platforms as possible to make sure we have no regressions from the previous
 release.  We need volunteers to do these tests.  This document is an attempt
-to provide a step-by-step walkthrough of what needs to be done.
-<br>You may want to read the <A HREF="../install/test.html">general
-instructions for testing</A> first.  These describe some steps necessary
-to set up the infrastructure needed to run the testsuite at all.
-<br>Once you have done that, proceed with these steps:
-<ul>
-<li> Download gcc-2.95.2 and the current testsuite:<nl>
-
-<br><A HREF=" ftp://gcc.gnu.org/pub/gcc/releases/gcc-2.95.2/gcc-2.95.2.tar.gz ">
-gcc-2.95.2.tar.gz</A>
-<br><A HREF=" ftp://gcc.gnu.org/pub/gcc/snapshots/2000-11-27/gcc-tests-20001127.tar.gz ">
-gcc-tests-20001127.tar.gz</A>
-<li>Extract both, then move the testsuite into the right place:
-<tt>
-  <br>rm -rf gcc-2.95.2/gcc/testsuite
-  <br>mv gcc-20001127/gcc/testsuite gcc-2.95.2/gcc/
-</tt>
-<li>Change into the directory <tt>"gcc-2.95.2/gcc/testsuite"</tt> and apply
-<A HREF="testsuite.diff">this patch</A> as follows:
-<tt>
-  <br>patch -p0 <testsuite.diff
-</tt>
-
-<li>Build the 2.95.2 release on all available targets (using <tt>"make
-bootstrap"</tt>).
-<li>Run the testsuite (<tt>"make -k check"</tt>), and send in the results.
-There's a script, "gcc-2.95.2/contrib/test_summary", which will apparently
-help you postprocess those results into a usable form.  If you run it like
-this (while in the toplevel build directory)
-<tt>
-  <br>gcc-2.95.2/contrib/test_summary | sh
-</tt>
-<br>it will automatically mail the results to the right place.
-</ul>
-
-The same thing will then have to be done for the 2.95.3 test releases which
-ought to start appearing shortly after Dec 17, 2000.  If you want, you can
-already do tests on the current branch; the CVS branch tag is
-<tt>"gcc-2_95-branch"</tt>.
-Don't forget to substitute the new testsuite on the branch as well.
+to provide a step-by-step walkthrough of what needs to be done.</p>
+
+<p>You may want to read the <a href="../install/test.html">general
+instructions for testing</a> first.  These describe some steps necessary
+to set up the infrastructure needed to run the testsuite at all.</p>
+
+<p>Once you have done that, proceed with these steps:</p>
+
+<ol>
+
+<li>Download gcc-2.95.2 and the current testsuite:
+<br><a href=" ftp://gcc.gnu.org/pub/gcc/releases/gcc-2.95.2/gcc-2.95.2.tar.gz ">
+gcc-2.95.2.tar.gz</a>
+<br><a href=" ftp://gcc.gnu.org/pub/gcc/snapshots/2000-11-27/gcc-tests-20001127.tar.gz ">gcc-tests-20001127.tar.gz</a>
+</li>
+
+<li><p>Extract both, then move the testsuite into the right place:</p>
+<blockquote><code>
+  rm -rf gcc-2.95.2/gcc/testsuite<br>
+  mv gcc-20001127/gcc/testsuite gcc-2.95.2/gcc/
+</code></blockquote>
+
+<li><p>Change into the directory "<code>gcc-2.95.2/gcc/testsuite</code>"
+and apply <a href="testsuite.diff">this patch</a> as follows:</p>
+<blockquote><code>
+  patch -p0 <testsuite.diff
+</code></blockquote>
+</li>
+
+<li>Build the 2.95.2 release on all available targets (using "<code>make
+bootstrap</code>").
+</li>
+
+<li><p>Run the testsuite ("<code>make -k check</code>"), and send in
+the results.  There's a script, "gcc-2.95.2/contrib/test_summary",
+which will apparently help you postprocess those results into a usable
+form.  If you run it like this (while in the toplevel build directory)</p>
+
+<blockquote><code>
+  gcc-2.95.2/contrib/test_summary | sh
+</code></blockquote>
+
+<p>it will automatically mail the results to the right place.</p>
+</li>
+</ol>
+
+<p>The same thing will then have to be done for the 2.95.3 test releases
+which ought to start appearing shortly after Dec 17, 2000.  If you want,
+you can already do tests on the current branch; the CVS branch tag is
+"<code>gcc-2_95-branch</code>".
+Don't forget to substitute the new testsuite on the branch as well.</p>


 </body>

