Re: [wwwdocs] Mention GIMPLE and RTL frontends in changes.html
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 > === > +GCC's already extensive self-test suite has gained some new > + capabilities, to further improve the reliability of the > compiler: > > Would "testsuite" be sufficient here? > > (Per codingconventions.html we use "testsuite" as opposed to "test > suite", as I just checked.) Changed. > + GCC now has has an internal unit testing API and a suite > of tests > +for programmatic self-testing of implementation > subsystems. > > 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
Re: [wwwdocs] Mention GIMPLE and RTL frontends in changes.html
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 === +GCC's already extensive self-test suite has gained some new + capabilities, to further improve the reliability of the compiler: Would "testsuite" be sufficient here? (Per codingconventions.html we use "testsuite" as opposed to "test suite", as I just checked.) + GCC now has has an internal unit testing API and a suite of tests +for programmatic self-testing of implementation subsystems. 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
[wwwdocs] Mention GIMPLE and RTL frontends in changes.html
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?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 - 1.46 +++ htdocs/gcc-7/changes.html 2 Feb 2017 21:47:21 - @@ -735,9 +735,6 @@ $ gcc -c test.c --param max-early-inline cc1: error: invalid --param name 'max-early-inliner-iteration'; did you mean 'max-early-inliner-iterations'? - GCC has gained an internal unit-testing framework, allowing for -more detailed testing of its implementation details. - Profile-guided optimization (PGO) instrumentation, as well as test coverage (GCOV), can newly instrument constructors (functions marks with __attribute__((constructor))), destructors and C++ constructors (and destructors) of classes that are used @@ -749,6 +746,25 @@ cc1: error: -pthread on command line would result in selection of atomic profile updating (when supports by a target). + +GCC's already extensive self-test suite has gained some new + capabilities, to further improve the reliability of the compiler: + + GCC now has has an internal unit testing API and a suite of tests +for programmatic self-testing of implementation subsystems. + 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 +https://gcc.gnu.org/onlinedocs/gccint/GIMPLE-Tests.html;> +GIMPLE representation (for testing higher-level +optimizations) and the +https://gcc.gnu.org/onlinedocs/gccint/RTL-Tests.html;> +RTL representation, allowing for more direct testing of +lower-level details, such as register allocation and instruction +selection. + +
