Remove some straightforward cases of unreachable code. I believe these are all break statements that have a return, goto, or another break immediately preceding them. It may not be possible to enable -Wunreachable-code by default. There are many places where we have code after CRASH() / NO_RETURN functions, return values after switches that return for all possible values, code that compiles differently on 32/64bit that statically eliminate branches (if sizeof(...)), debug only code enabled/disabled by static booleans that are false, and more. I did file some bugs on real cases of unreachable code that this caught; nothing significant.
Created attachment 224985 [details] [PATCH] Proposed Fix
Comment on attachment 224985 [details] [PATCH] Proposed Fix Clearing flags on attachment: 224985 Committed r164553: <http://trac.webkit.org/changeset/164553>
All reviewed patches have been landed. Closing bug.