https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Since r12-2468 it should be impossible for those members to be uninitialized, and valgrind shows no uninitialized data. I think this is a compiler bug. (In reply to Martin Liška from comment #1) > Started with r12-6216-g5a431b60d1f22199. That only changed how -Wsystem-headers affects warnings (and not an improvement IMHO). The bogus warning was already present before then if you use -Wsystem-headers