https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82365
--- Comment #9 from rguenther at suse dot de <rguenther at suse dot de> --- On Fri, 1 Dec 2017, arnd at linaro dot org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82365 > > --- Comment #8 from Arnd Bergmann <arnd at linaro dot org> --- > I noticed that I never resubmitted my workaround for the kernel for this > problem, and nothing happened on the gcc side either. To make sure I capture > the situation correctly in the kernel patch changelog, could I get an > clarification on whether this is something the gcc developers think might get > addressed before the gcc-8 release, or whether I should assume it is too minor > to take up anyone's time? Too complicated at this point for questionable gain (easy source workaround possible).
