On Wed, 20 May 2026 at 17:31, Joseph Myers wrote: > > On Wed, 20 May 2026, Richard Biener via Gcc wrote: > > > I'm OK with that that though moving the diagnostics earlier might be another > > option. But once they are no longer in -Wall I fear nobody will enable them > > and so we can as well eliminate the then unused (and actually unmaintained > > for large parts) code ... > > You could put them in -Wextra. -Wall is supposed to be "all the warnings > about constructions that some users consider questionable, and that are > easy to avoid (or modify to prevent the warning), even in conjunction with > macros", while -Wextra includes some warnings for "constructions that are > necessary or hard to avoid in some cases, and there is no simple way to > modify the code to suppress the warning" (which seems like a reasonable > match for the issues with false positives for these warnings).
I agree. And the people who find them useful can enable them for their own (automated or manual) testing via ~/.dejagnurc or similar methods. I run the libstdc++ testsuite with options to check every combination of -std and assertions on/off and old/new std::string ABI, but I don't expect everybody running the testsuite to do that. It finds problems that get missed otherwise, but we don't need to make the testsuite 10 times slower for everybody to get that benefit. Only one person (or buildbot) needs to run with all the extra options.
