https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44677
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
I haven't thought through the implementation challenges but defining the
extended -Wunused-but-set-variabl rule that's being suggested here seems
straightforward: every write to an object must be followed by another access to
it (either read or write). If not, it's diagnosed.
This seems analogous to the -Wuninitialized checker/rule that might be stated
as: the first read of an object must be preceded by a write to it.
