<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >Crap. No unreachable code warning in gcc anymore. <div><br></div><div><br></div><div>I think that is an astonishing failure. </div><div><br></div><div>As a developer, I rely on that warning because unreachable code is ALWAYS a mistake. </div><div><br></div><div><br></div><br><br><br>-------- Original message --------<br>From: Nicolas Rachinsky <crypto-2@ml.turing-complete.org> <br>Date: 03/04/2014 04:23 (GMT-08:00) <br>To: Bear <bear@sonic.net> <br>Cc: dennis.hamilton@acm.org,'Cryptography' <cryptography@metzdowd.com> <br>Subject: Re: [Cryptography] The GOTO Squirrel! [was GOTO Considered Harmful] <br> <br><br>* Bear <bear@sonic.net> [2014-03-03 11:04 -0800]:<br>> On Fri, 2014-02-28 at 17:03 -0800, Dennis E. Hamilton wrote:<br>> <br>> <br>> > <br>> > A pretty-printer (or any IDE that reflows indentation) would point it out. <br>> > <br>> > So would a modern IDE that identifies unreachable code. <br>> > <br>> > Any practical code-coverage testing would reveal it too.<br>> <br>> Okay, I have to say this despite the complaints on this <br>> list about how common TERRIBLE security practices may be.<br>> <br>> This is completely over the top. There is no way that this<br>> could possibly be accidental.<br>> <br>> In point of fact, I know of no commonly used or commercially <br>> sold compiler that fails to emit unreachable-code warnings <br>> by default. Therefore I do not believe that this could be <br>> anything but deliberate. I would be willing to state exactly <br>> that in a court of law.<br><br>Ho about gcc?<br><br>http://gcc.gnu.org/ml/gcc-help/2011-05/msg00360.html<br>|The -Wunreachable-code has been removed, because it was unstable:<br>|it relied on the optimizer, and so different versions of gcc would<br>|warn about different code. The compiler still accepts and ignores<br>|the command line option so that existing Makefiles are not broken.<br>|In some future release the option will be removed entirely.<br><br>Nicolas<br>_______________________________________________<br>The cryptography mailing list<br>cryptography@metzdowd.com<br>http://www.metzdowd.com/mailman/listinfo/cryptography<br><br></body>