https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82100
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-09-04
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=46476
Summary|gcc cannot detect |gcc does not warn about
|unreachable code even when |code that is unreachable
|-Wunreachable-code is in |due to conflicting
|effect |conditions [subset of
| |reviving
| |-Wunreachable-code]
Ever confirmed|0 |1
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
Bug 46476 is related (which you've already commented in), but that's just about
the case for code after return or break statements. Confirming this as a
separate issue that maybe gcc should have a separate flag for?
