On Wed, Apr 4, 2018 at 8:08 AM, Gerald Pfeifer <ger...@pfeifer.com> wrote: > On Tue, 3 Apr 2018, Bin Cheng wrote: >> Option -ftree-loop-distribution is improved and enabled by default at >> -O3 for GCC8. This patch describes the change, is it OK? > > Index: htdocs/gcc-8/changes.html > =================================================================== > + Classical loop nest optimization pass > <code>-ftree-loop-distribution</code> > > "The classic loop nest..." (i.e., add the article and I believe classic > is more appropriate than classical which connotates the arts,...). > > + It supports loop nest distribution in some restricted scenarios; it also > + supports cancellable innermost loop distribution with loop versioning > + under runtime alias checks. > > I believe that would be "run-time" (per codingconventions.html)? > > Fine with the change above and considering the second comment. Thanks for the suggestions, attachment is the updated change.
Thanks, bin > > Thank you, > Gerald
Index: htdocs/gcc-8/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v retrieving revision 1.51 diff -u -r1.51 changes.html --- htdocs/gcc-8/changes.html 3 Apr 2018 06:52:04 -0000 1.51 +++ htdocs/gcc-8/changes.html 4 Apr 2018 08:55:11 -0000 @@ -101,6 +101,13 @@ are enabled by default at <code>-O3</code> and above. </li> <li> + The classic loop nest optimization pass <code>-ftree-loop-distribution</code> + has been improved and enabled by default at <code>-O3</code> and above. + It supports loop nest distribution in some restricted scenarios; it also + supports cancellable innermost loop distribution with loop versioning + under run-time alias checks. + </li> + <li> The new option <code>-fstack-clash-protection</code> causes the compiler to insert probes whenever stack space is allocated statically or dynamically to reliably detect stack overflows and