public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <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:10:00 -0000 [thread overview] Message-ID: <bug-7652-4-QTSevHxmSB@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 #23 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Michael Chapman from comment #21) > Created attachment 32716 [details] > Proposed patch > > Patch to enable warnings (-Wswitch-fallthrough) when a switch case falls > through. Enabled by -Wall. Thanks! Patches need to be submitted to gcc-patches@gcc.gnu.org with a Changelog after bootstrapping and regression testing. The patch is missing a testcase for the regression testsuite showing in which cases it should warn and in which cases it should not. First of all, you need to have a copyright assignment in place with the FSF. This is slightly annoying to do the first time, but you only have to do it once for all GNU projects. See: http://gcc.gnu.org/contribute.html About the patch: +int +c_stmt_ends_with_goto (tree t) This should return 'bool' +{ + if (TREE_CODE (t) == GOTO_EXPR) + return TRUE; + if (TREE_CODE (t) == BIND_EXPR) + return c_stmt_ends_with_goto (tsi_stmt (tsi_last (BIND_EXPR_BODY (t)))); + return FALSE; +} You can use 'true' and 'false' + +/* Handle -Wswitch-fallthrough */ +void +c_do_switch_fallthru_warnings (tree body) +{ + tree_stmt_iterator i; + tree previous_stmt = NULL; + tree previous_label = NULL; + tree stmts = BIND_EXPR_BODY (body); I think it would be worthwhile to add: if (!warn_switch_fallthrough) return; to avoid going through the loop if we are not going to warn anyway. +Wswitch-fallthrough +C ObjC C++ ObjC++ Var(warn_switch_fallthrough) Warning LangEnabledBy(C ObjC C++ ObjC++,Wall) +Warn about switch cases which fall through to the next case + This says that the warning is available in C++, but I don't see any code in your patch that calls the new function from the C++ FE. It would be nice to have the same warning in C++. This will allow testing how noisy it is in GCC itself, for instance. But you (or someone else) could do that as a follow-up. >From gcc-bugs-return-450267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 30 16:11:49 2014 Return-Path: <gcc-bugs-return-450267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 26929 invoked by alias); 30 Apr 2014 16:11:49 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 26847 invoked by uid 48); 30 Apr 2014 16:11:45 -0000 From: "redi at gcc dot gnu.org" <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:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: unknown X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-7652-4-lF15yFbDVj@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-7652-4@http.gcc.gnu.org/bugzilla/> References: <bug-7652-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-04/txt/msg02287.txt.bz2 Content-length: 385 http://gcc.gnu.org/bugzilla/show_bug.cgi?idv52 --- Comment #24 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Matthew Woehlke from comment #22) > [[gcc:fallthrough]] // suppress warning for fall-through to 'case C' N.B. the attribute-namespace for GNU extensions is "gnu" I agree that the attribute is essential before such warning could be enabled by -Wall
next prev parent reply other threads:[~2014-04-30 16:10 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 2014-04-30 16:10 ` manu at gcc dot gnu.org [this message] 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-QTSevHxmSB@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).