https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78000
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- As I've said before, we have to stop doing individual ad hoc fixes for bugs like this; there are too many of them. We have to work out the general principles for which warnings should or should not be inhibited for macros from system headers (roughly, the question is whether the macro or its user is responsible for the warning) and then design APIs that make it easy to get it right for each individual warning - and review existing warnings systematically. Failing that, disable inhibiting such warnings for macros from system headers globally.
