[wwwdocs] Mention GIMPLE and RTL frontends in changes.html

[wwwdocs] Mention GIMPLE and RTL frontends in changes.html

[David Malcolm]

[-- Attachment #1: Type: text/plain, Size: 322 bytes --]

This patch to the website moves the section about the selftest suite to
the bottom of "Other significant improvements" section, and rewrites it
to also cover the GIMPLE and RTL "frontends", and tries to couch these
changes in terms of the benefit to the end-user (i.e. a more reliable
compiler).

Validates.

OK to commit?

[-- Attachment #2: test-suite.patch --]
[-- Type: text/x-patch, Size: 2230 bytes --]

Index: htdocs/gcc-7/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v
retrieving revision 1.46
diff -u -p -r1.46 changes.html
--- htdocs/gcc-7/changes.html	28 Jan 2017 01:15:53 -0000	1.46
+++ htdocs/gcc-7/changes.html	2 Feb 2017 21:47:21 -0000
@@ -735,9 +735,6 @@ $ gcc -c test.c --param max-early-inline
 cc1: <span class="boldred">error:</span> invalid --param name <b>'max-early-inliner-iteration'</b>; did you mean <b>'max-early-inliner-iterations'</b>?
 </pre></blockquote></li>
 
-  <li>GCC has gained an internal unit-testing framework, allowing for
-    more detailed testing of its implementation details.</li>
-
   <li>Profile-guided optimization (PGO) instrumentation, as well as test coverage (GCOV),
       can newly instrument constructors (functions marks with <code>__attribute__((constructor)))</code>,
       destructors and C++ constructors (and destructors) of classes that are used
@@ -749,6 +746,25 @@ cc1: <span class="boldred">error:</span>
       <code>-pthread</code> on command line would result in selection of atomic
       profile updating (when supports by a target).
   </li>
+  <li>
+    <p>GCC's already extensive self-test suite has gained some new
+      capabilities, to further improve the reliability of the compiler:</p>
+    <ul>
+      <li>GCC now has has an internal unit testing API and a suite of tests
+        for programmatic self-testing of implementation subsystems.</li>
+      <li>GCC's C frontend has been extended so that it can parse dumps of
+        GCC's internal representations, allowing for DejaGnu tests
+        that more directly exercise specific optimization passes.  This
+        covers both the
+        <a href="https://gcc.gnu.org/onlinedocs/gccint/GIMPLE-Tests.html">
+        GIMPLE representation</a> (for testing higher-level
+        optimizations) and the
+        <a href="https://gcc.gnu.org/onlinedocs/gccint/RTL-Tests.html">
+        RTL representation</a>, allowing for more direct testing of
+        lower-level details, such as register allocation and instruction
+        selection.</li>
+    </ul>
+  </li>
 </ul>
 
 <!-- <h2><a name="7.1">GCC 7.1</a></h2>

Re: [wwwdocs] Mention GIMPLE and RTL frontends in changes.html

[Gerald Pfeifer]

On Thu, 2 Feb 2017, David Malcolm wrote:
> This patch to the website moves the section about the selftest suite to
> the bottom of "Other significant improvements" section, and rewrites it
> to also cover the GIMPLE and RTL "frontends", and tries to couch these
> changes in terms of the benefit to the end-user (i.e. a more reliable
> compiler).

Index: htdocs/gcc-7/changes.html
===================================================================
+    <p>GCC's already extensive self-test suite has gained some new
+      capabilities, to further improve the reliability of the compiler:</p>

Would "testsuite" be sufficient here?

(Per codingconventions.html we use "testsuite" as opposed to "test 
suite", as I just checked.)

+      <li>GCC now has has an internal unit testing API and a suite of tests
+        for programmatic self-testing of implementation subsystems.</li>

Omit "implementation"?

Those are genuine questions (where I feel a little stronger about 
the former than the latter), i.e., while I personally would make 
those changes, I am not making this a requirement of my review.

The patch is okay, just consider the above, please.

Thanks,
Gerald

Re: [wwwdocs] Mention GIMPLE and RTL frontends in changes.html

[David Malcolm]

On Fri, 2017-02-03 at 08:09 +0100, Gerald Pfeifer wrote:
> On Thu, 2 Feb 2017, David Malcolm wrote:
> > This patch to the website moves the section about the selftest
> > suite to
> > the bottom of "Other significant improvements" section, and
> > rewrites it
> > to also cover the GIMPLE and RTL "frontends", and tries to couch
> > these
> > changes in terms of the benefit to the end-user (i.e. a more
> > reliable
> > compiler).
> 
> Index: htdocs/gcc-7/changes.html
> ===================================================================
> +    <p>GCC's already extensive self-test suite has gained some new
> +      capabilities, to further improve the reliability of the
> compiler:</p>
> 
> Would "testsuite" be sufficient here?
> 
> (Per codingconventions.html we use "testsuite" as opposed to "test 
> suite", as I just checked.)

Changed.

> +      <li>GCC now has has an internal unit testing API and a suite
> of tests
> +        for programmatic self-testing of implementation
> subsystems.</li>
> 
> Omit "implementation"?
> 
> Those are genuine questions (where I feel a little stronger about 
> the former than the latter), i.e., while I personally would make 
> those changes, I am not making this a requirement of my review.
> 
> The patch is okay, just consider the above, please.

I tried a few variants here, but in the end I considered your
suggestion as the cleanest; thanks!

Committed

Dave