https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92479
--- Comment #4 from tangyixuan <tangyixuan at mail dot dlut.edu.cn> --- (In reply to Eric Gallager from comment #2) > (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) yeah, -Wunreachable-code-break and -Wunreachable-code-break are two different options in clang, which are also seperated from -Wunreachable-code. I do not know whether gcc could detect the cases. Gcc would be prefect with your efforts.
