https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87281
--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- No idea. I ran all-languages builds for all glibc ABIs as a one-off when adding the --full-gcc option to build-many-glibcs.py, and reported the GCC bugs that showed up. The idea was that since maintainers of such language libraries (and of libsanitizer) had concerns about glibc header changes sometimes breaking the build of those libraries, I'd provide the facility in build-many-glibcs.py for people with those concerns to run a bot testing them with current glibc, in order to detect problems quickly rather than only after an issue gets into a glibc release. But I was definitely leaving it up to people with such concerns to deal with running the bot, and I don't think anyone has taken up doing so.
