https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83990
--- Comment #3 from Tony E Lewis <TonyELewis at hotmail dot com> --- Just to be clear... I don't think it's _necessarily_ a problem that the warning is being triggered in this particular context (because I'm not in a position to judge that). The core problem I wish to highlight is that, despite being triggered within a system header, the warning isn't being silenced as I would expect. And my suspicion is that this is caused by the source location info having been lost so the location cannot be recognised as within a system header (as has been hypothesised for bug 83591). (I also wish to highlight that the lack of source location info makes the warning very much harder to respond to.)
