https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86275
--- Comment #5 from Florian Weimer <fw at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #4) > The question is if this is a problem with recent kernel headers and any > glibc, or e.g. both latest glibc and 2.27; if yes, then we probably need > some workaround in gcc too. If it is only latest unreleased glibc, then it > is fine to be fixed only there. I don't think this issue applies to glibc 2.27, even though my glibc patch does.
