https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92479
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=46476,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=82100
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> The code for Wunreachable-code was removed a long time ago (around 5-10
> years ago).
There are some other bugs open about reviving -Wunreachable-code. There's bug
46476 for -Wunreachable-code-return, which I thought this was a dup of at
first, but I guess since -Wunreachable-code-break has a different name that
this can stay separate. If we're adding bugs for each of clang's sub-options
for -Wunreachable-code, then I guess it might be worth creating a bug for
-Wunreachable-code-loop-increment, too. (There's also bug 82100 for code that's
unreachable due to conflicting conditions)
