On Fri, 3 Feb 2017, Gerald Pfeifer wrote: > Of course, an innocent grep after providing this input in a review > of a patch by David revealed that we have a number more cases where > we used "test suite" instead of "testsuite".
And now a recursive grep. Applied. Gerald Index: bugs/minimize.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/minimize.html,v retrieving revision 1.8 diff -u -r1.8 minimize.html --- bugs/minimize.html 28 Jun 2014 08:14:41 -0000 1.8 +++ bugs/minimize.html 3 Feb 2017 08:14:32 -0000 @@ -26,7 +26,7 @@ <li>GCC developers prefer bug reports with small, portable test cases.</li> - <li>Minimized test cases can be added to the GCC test suites.</li> + <li>Minimized test cases can be added to the GCC testsuite.</li> </ul> <p>There are basically two methods: either <a href="#direct">directly Index: projects/beginner.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v retrieving revision 1.64 diff -u -r1.64 beginner.html --- projects/beginner.html 28 May 2016 20:40:35 -0000 1.64 +++ projects/beginner.html 3 Feb 2017 08:14:33 -0000 @@ -39,7 +39,7 @@ <h2>Bug patrol</h2> <p>These projects all have to do with bugs in the compiler, and our -test suite which is supposed to make sure no bugs come back.</p> +testsuite which is supposed to make sure no bugs come back.</p> <ul> <li>Analyze failing test cases. @@ -92,7 +92,7 @@ <p>It's likely that the same test has been added more than once, over the years. You'd need to figure out a sensible definition of "the same test" that can be checked mechanically, then write a program that -does that check, and run it against the entire test suite.</p> +does that check, and run it against the entire testsuite.</p> </li> <li>Perform additional GCC testing. Index: testing/index.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/testing/index.html,v retrieving revision 1.37 diff -u -r1.37 index.html --- testing/index.html 29 Jun 2014 18:50:44 -0000 1.37 +++ testing/index.html 3 Feb 2017 08:14:33 -0000 @@ -16,7 +16,7 @@ For information about testsuite organization and adding new tests, see <a href="https://gcc.gnu.org/onlinedocs/gccint/Testsuites.html";> Test Suites</a> in the GCC Internals manual and the README files in -the test suite directories.</p> +the testsuite directories.</p> <h2>Current efforts</h2> Index: testing/testing-blitz.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/testing/testing-blitz.html,v retrieving revision 1.7 diff -u -r1.7 testing-blitz.html --- testing/testing-blitz.html 27 May 2016 20:04:50 -0000 1.7 +++ testing/testing-blitz.html 3 Feb 2017 08:14:33 -0000 @@ -17,11 +17,11 @@ href="https://sourceforge.net/projects/blitz/files/";>Blitz++ download page</a> at SourceForge is a 2.0 MB file. The uncompressed distribution comprises 10.5 MB of source files. Building and running the -test suite adds an additional 75 or so MB of object files +testsuite adds an additional 75 or so MB of object files and executables to this, and building the Blitz++ example programs adds another 50 MB.</p> -<p>Building and running the Blitz++ test suite on a 750 Mhz +<p>Building and running the Blitz++ testsuite on a 750 Mhz Pentium III laptop takes 17 minutes. Building the Blitz++ example programs takes another 20 minutes.</p>
