https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87822
--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 31 Oct 2018, redi at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87822 > > --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- > (In reply to Richard Biener from comment #5) > > Unfortunate :/ Can you add a 6.5 specific note to 6.5/changes.html? > > Will do. > > I think it would also be good to commit the fix to the gcc-6-branch, even if > it's closed, so it can be picked up from there if needed. Hmm. I think it may be better to provide the fix as patch, referenced from the changes.html note? > Do we even want to consider a 6.6 release, or just officially bless a 6.5.1 > snapshot post-fix? Neither of that (there are no further snapshots from the branch anyways). Since 6.5 isn't supported anymore I'd rather point people to 7.x.
