https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92479
--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> --- On Tue, 30 Nov 2021, egallager at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92479 > > --- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> --- > (In reply to Richard Biener from comment #9) > > I'm going to re-interpret -Wunreachable-code-{return,break} to mean to > > diagnose unreachable code _after_ a return stmt or a break stmt. It really > > looks like clang went out with a hammer, assigning a different option to > > each diagnostic invocation with a different text ... > > I actually appreciate that about clang; additional warning flag granularity > helps to break warning-silencing tasks down in to more-easily manageable parts > when there are a lot of similar warnings. Sometimes I might want to only focus > on one while saving the other for later. I see. Just in this case the choice to differentiate seems silly.
