install.texi (Testing): Mention test result links from build status pages.

2003-03-24  Janis Johnson  <janis187@us.ibm.com>

	* doc/install.texi (Testing): Mention test result links from build
	status pages.

From-SVN: r64811

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 0e10cb312f08251f914cde35c0d4631b2542dbd2..189a3d2212c737a45930a135db978b2e3276446a 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2003-03-24  Janis Johnson  <janis187@us.ibm.com>
+
+       * doc/install.texi (Testing): Mention test result links from build
+       status pages.
+
 2003-03-24  Mark Mitchell  <mark@codesourcery.com>
 
        * function.c (put_var_into_stack): Change bool parameter to int.

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index d5fc5595198fa1f4bc29bac23a40dce54cfdfa6a..f5d1dca4e29bbc379879e9824d7746fdc49267d5 100644 (file)
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -1213,6 +1213,9 @@ Before you install GCC, we encourage you to run the testsuites and to
 compare your results with results from a similar configuration that have
 been submitted to the
 @uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
+Some of these archived results are linked from the build status lists
+at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
+reports a successful build runs the testsuites and submits the results.
 This step is optional and may require you to download additional software,
 but it can give you confidence in your new GCC installation or point out
 problems before you install and start using your new GCC.