https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82520
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-10-12
CC| |msebor at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=69433,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=71924,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=81811
Ever confirmed|0 |1
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
There are a number of classes of instances of this problem that GCC doesn't
detect but arguably should and possibly could. Examples include: pr69433,
pr71924, and pr81811. Detecting all of them may not be straightforward or
even feasible but improving on the status quo certainly is possible. This case
does seem like one of the harder ones to catch. Confirming with that caveat.
