https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85180
--- Comment #19 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 9 May 2018, romain.naour at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85180 > > Romain Naour <romain.naour at gmail dot com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |romain.naour at gmail dot com > > --- Comment #18 from Romain Naour <romain.naour at gmail dot com> --- > (In reply to Richard Biener from comment #17) > > (In reply to romain.naour from comment #16) > > > Hi, > > > > > > gcc 7.3.0 is affected by this bug but only on microblaze architecture, see > > > [1]. > > > Do you plan to backport this patch on gcc 7.x? > > > It is safe to do so without take the risk to break something with other > > > architecture or optimization level? > > > > > > Best regards, > > > Romain > > > > > > [1] http://lists.busybox.net/pipermail/buildroot/2018-April/220156.html > > > > The bug isn't a regression so technically it doesn't qualify. OTOH it > > looks reasonably safe to backport and the bug is annoying. Jakub, would > > you be ok with a backport? > > Ping? Jakub said it doesn't qualify give it's too risky.
