public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mw_triad at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/7652] -Wswitch-break : Warn if a switch case falls through Date: Wed, 30 Apr 2014 16:09:00 -0000 [thread overview] Message-ID: <bug-7652-4-OxXuoJ3NHU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-7652-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7652 --- Comment #22 from Matthew Woehlke <mw_triad at users dot sourceforge.net> --- Thanks for the patch. However, one thing I am not seeing is an easy way to suppress the warning for a specific occurrence (a la [[clang:fallthrough]]). Can that be added also? (Or is it there and I miss something?) Ideally this would work like: switch (expr) { case A: // empty body, no warning case B: ... [[gcc:fallthrough]] // suppress warning for fall-through to 'case C' case C: ... break; case D: ... // will warn here default: ... break; }
next prev parent reply other threads:[~2014-04-30 16:09 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-7652-4@http.gcc.gnu.org/bugzilla/> 2011-02-02 1:04 ` alsuren+gcc at gmail dot com 2011-05-09 14:48 ` barnes.leo at gmail dot com 2011-07-29 13:29 ` daniel.marjamaki at gmail dot com 2012-02-21 1:04 ` eric at brouhaha dot com 2012-02-21 1:14 ` eric at brouhaha dot com 2012-07-14 4:55 ` pinskia at gcc dot gnu.org 2012-07-14 11:54 ` redi at gcc dot gnu.org 2012-07-14 15:15 ` david at doublewise dot net 2012-09-17 22:02 ` alexfh at google dot com 2012-09-18 11:12 ` manu at gcc dot gnu.org 2012-11-26 22:49 ` arthur.j.odwyer at gmail dot com 2012-11-26 23:03 ` arthur.j.odwyer at gmail dot com 2013-06-23 6:44 ` dcb314 at hotmail dot com 2013-06-23 10:38 ` manu at gcc dot gnu.org 2013-06-23 12:21 ` jasonwucj at gmail dot com 2014-02-16 13:18 ` jackie.rosen at hushmail dot com 2014-04-30 15:45 ` michael.chapman at cortus dot com 2014-04-30 16:09 ` mw_triad at users dot sourceforge.net [this message] 2014-04-30 16:10 ` manu at gcc dot gnu.org 2014-04-30 16:18 ` fweimer at redhat dot com 2014-04-30 16:23 ` mpolacek at gcc dot gnu.org 2014-04-30 16:35 ` alexfh at google dot com 2014-04-30 16:40 ` manu at gcc dot gnu.org 2014-04-30 17:04 ` mw_triad at users dot sourceforge.net 2014-04-30 17:20 ` michael.chapman at cortus dot com 2014-09-23 7:25 ` m.j.thayer at googlemail dot com [not found] <bug-7652-1366@http.gcc.gnu.org/bugzilla/> 2010-03-04 20:48 ` pinskia at gcc dot gnu dot org [not found] <20020820073602.7652.ac131313@redhat.com> 2004-07-29 9:43 ` brendan at zen dot 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-7652-4-OxXuoJ3NHU@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).