https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64883
--- Comment #42 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to nightstrike from comment #41)
> It seems to me that the test itself is a bit overzealous. If the intent is
> to ensure just that libstdc++ sources don't use certain words, well that's
> not entirely what is happening.
No, the intent is to ensure that this valid code compiles:
#define noreturn 1 2 3
#include <iostream>
int main() { }
Not "compiles, except for the bits that aren't from libstdc++" just "compiles".
That's a valid program, and should compile.
But obviously libstdc++ doesn't control everything that <iostream> includes,
and so it might fail for reasons outside libstdc++'s control. Those are still
bugs, but they should be reported to the upstream libc (not to libstdc++).
If mingw causes that valid program to fail, it's a bug in mingw. Please report
it. If mingw won't fix it, the libstdc++ test should be marked xfail for that
target, or we can not test for some attributes on mingw (at the risk of
libstdc++ starting to accidentally use that in mingw-specific code that doesn't
get tested on other targets).
