On Thu, Oct 17, 2019 at 8:47 AM Arnd Bergmann <arnd@xxxxxxxx> wrote: > > For the record, that seems to mean that moving to gcc-4.8 > would likely not cause a lot of problems and would let us do > some other cleanups, but unfortunately would not help with > the compound literals. Yeah, that's certainly less than wonderful. That said, there's no way in hell we'll support gcc-4 for another 7 years (eg Suse 12-sp4), so at _some_ point the EOL dates aren't even relevant any more. But it does look like we can't just say "gcc-5.1 is ok". Darn. Linus