https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69723
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Peter VARGA from comment #3)
> thank you for the explanation. But honestly, the "definition" when to warn
> is in my eyes wrong. Even var++ is reading and then setting the variable in
> this case it does NOT make sense!
Replace unused++ with unused = unused + 1. If we want GCC to warn about that,
we would need, for every VAR = EXPRESSION, check if VAR appears in EXP. It may
be possible, but it probably needs to keep track of VAR while parsing EXP,
which may require touching an awful number of functions.
