https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94629
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #15 from Martin Sebor <msebor at gcc dot gnu.org> ---
I agree (unsurprisingly) that adding warnings for some of the problems noted in
the article would be useful, not just for GCC itself but other projects. I
don't have the impression that uncovering them would benefit from the sort of
interprocedural traversal the analyzer is mainly supposed to be good for.
Since many fewer projects run the analyzer often enough or ever due to the
costs, implementing these warnings there would make them unavailable to the
majority of users, or delay finding these basic problems when they're the
cheapest to fix: before they are committed into the repository.
