public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/92479] missing warnings for unreachable codes with break (i.e. revive the subset of -Wunreachable-code that fits under clang's -Wunreachable-code-break) Date: Thu, 20 Jan 2022 18:48:51 +0000 [thread overview] Message-ID: <bug-92479-4-a78clUvrWR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92479-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92479 David Binderman <dcb314 at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcb314 at hotmail dot com --- Comment #12 from David Binderman <dcb314 at hotmail dot com> --- Interestingly, both gcc and clang have nothing to say about this code: extern void g( int); void f( int a) { if (a >= 0) { if (a < 0) { g(a); } } } $ /home/dcb/gcc/results/bin/gcc -c -g -O2 -Wall -Wextra -Wunreachable-code jan20e.cc $ cppcheck finds the problem: $ cppcheck --enable=all jan20e.cc Checking jan20e.cc ... jan20e.cc:10:9: warning: Opposite inner 'if' condition leads to a dead code block. [oppositeInnerCondition] if (a < 0) ^ jan20e.cc:8:8: note: outer condition: a>=0 if (a >= 0) ^
next prev parent reply other threads:[~2022-01-20 18:48 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92479-4@http.gcc.gnu.org/bugzilla/> 2021-11-24 19:06 ` egallager at gcc dot gnu.org 2021-11-24 19:07 ` egallager at gcc dot gnu.org 2021-11-29 14:04 ` rguenth at gcc dot gnu.org 2021-11-29 14:10 ` rguenth at gcc dot gnu.org 2021-11-30 5:20 ` egallager at gcc dot gnu.org 2021-11-30 8:12 ` rguenther at suse dot de 2022-01-20 18:48 ` dcb314 at hotmail dot com [this message] 2022-01-20 18:51 ` dcb314 at hotmail dot com 2022-01-22 21:27 ` egallager at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-92479-4-a78clUvrWR@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).