https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84495
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Wed, Feb 21, 2018 at 10:44:07AM +0000, tkoenig at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84495 > > Thomas Koenig <tkoenig at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |tkoenig at gcc dot gnu.org > > --- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- > This looks like a duplicate of PR81116, fixed by r251125. > > This is not a regression, and in genereal (we have played loose with > this rule) we are not supposed to backport. > > Opinions? > Release Manager would probably say that it is up the Fortran Maintainers on whether something should be backported. If I have a patch on trunk that applies to the branch(es) with minimum effort, I tend to backport to keep code in sync.
