News for hackers. Stuff that matters.
Re:About the security content of iOS 7.0.6 by acdha on Saturday February 22, 2014 @09:57AM (#7282196)
> Don't C compilers warn about code that is never executed?

Not by default. On both GCC and Clang this kind of error isn't caught using -Wall or even -Wextra - you have to explicitly opt-in using -Wunreachable-code. It'd really be nice if that changed and Clang basically had close to -Weverything on by default and required you to opt out, preferably with something like `#pragma ALLOW_SHODDY_<category>` per file to put some pressure on C programmers not to just continue ignoring errors rather than fixing them.

Re:About the security content of iOS 7.0.6 by gsnedders on Saturday February 22, 2014 @10:25AM (#7282295)
In the latest GCC releases, -Wunreachable-code has been removed (the option still exists but is silently ignored for compat with existing Makefiles), as its output varied so much between releases (depending on what got optimized away).
Re:About the security content of iOS 7.0.6 by acdha on Saturday February 22, 2014 @10:49AM (#7282390)
I'd hope after this someone brings it back in some form – it's an incredibly useful tool and a diversity of implementations would be great for security-critical code.