https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104854
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> --- Moving warnings into the analyzer and scaling it up to be able to run by default, during development, sounds like a good long-term plan. Until that happens, rather than gratuitously removing warnings that we've added over the years, just because they fall short of the ideal 100% efficacy (as has been known and documented), making them easier to control seems like a better approach.
