https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86275
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- 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.
