https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112358
--- Comment #8 from Joseph S. Myers <jsm28 at gcc dot gnu.org> --- If it's a false positive, it's reasonable to work around in glibc using the libc-diag.h macros (DIAG_PUSH_NEEDS_COMMENT / DIAG_IGNORE_NEEDS_COMMENT / DIAG_POP_NEEDS_COMMENT) - but that would need an appropriately detailed comment explaining why it's a false positive and the code path implied by the warning isn't actually possible.
