x86_64 glibc has started to use it since the 2.43 release, but is
expected to fix it before the 2.44 release.
Link: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=b9579342c68b#patch67
libstdc++-v3/ChangeLog:
* testsuite/17_intro/badnames.cc (__unused): Do not define.
* testsuite/17_intro/names.cc [glibc == 2.43] (__unused): Undef.
Co-authored-by: Jonathan Wakely <jwakely@redhat.com>
// BSD adds:
#define __used __used is a BADNAME
-#define __unused __unused is a BADNAME
+ // __unused (glibc uses this so can't test here)
// __inline (glibc uses this so can't test here)
// _Complex (glibc uses this so can't test here)
#define __istype __istype is a BADNAME
#if defined (__linux__) || defined (__gnu_hurd__)
#if __has_include(<features.h>)
#include <features.h>
-#if __GLIBC__ == 2 && __GLIBC_MINOR__ < 19
+#if __GLIBC__ == 2 && (__GLIBC_MINOR__ < 19 || __GLIBC_MINOR__ == 43)
// Glibc defines this prior to 2.19
#undef __unused
#endif