On Thu, Jul 13, 2017 at 09:26:25PM +0200, Uros Bizjak wrote: > IMO, we should change only gcc-7 release branch, so developers can > test for gcc-7.2+ to determine which release swapped arguments of > mentioned intrinsics.
Agreed. > The attached doc patch adds commented-out generic gcc-7.2 entry plus > the above target-specific change. > > OK for branch? Ok for wwwdocs, with a nit: > Index: htdocs/gcc-7/changes.html > =================================================================== > RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v > retrieving revision 1.85 > diff -u -r1.85 changes.html > --- htdocs/gcc-7/changes.html 10 May 2017 11:39:41 -0000 1.85 > +++ htdocs/gcc-7/changes.html 13 Jul 2017 19:19:02 -0000 > @@ -1230,5 +1230,25 @@ > complete (that is, it is possible that some PRs that have been fixed > are not listed here).</p> > > +<!-- .................................................................. --> > +<!-- > +<h2><a name="7.2">GCC 7.2</a></h2> > + > +<p>This is the <a > href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=7.2">list > +of problem reports (PRs)</a> from GCC's bug tracking system that are > +known to be fixed in the 7.2 release. This list might not be > +complete (that is, it is possible that some PRs that have been fixed > +are not listed here).</p> > + > +<h3>Target Specific Changes</h3> > + > +<h4>IA-32/x86-64</h4> > + <ul> > + <li>The argument order of _subborrow_u32 and _subborow_u64 s/borow/borrow/ > + intrinsics has been changed to follow the latest update > + to the reference documentation.</li> > + </ul> > +--> > + > </body> > </html> Jakub