public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ami at fischman dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/20681] [4.3/4.4/4.5/4.6 Regression] wrong "control reaches" warning with switches Date: Thu, 24 Feb 2011 00:59:00 -0000 [thread overview] Message-ID: <bug-20681-4-lSZNfFIkLj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-20681-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20681 --- Comment #29 from Ami Fischman <ami at fischman dot org> 2011-02-23 23:35:45 UTC --- Further reduced test case from dup bug 47864: $ nl t.cc ; g++ -finstrument-functions -Wreturn-type -Werror -c t.cc 1 int foo(int type) { 2 switch(type) { 3 case 0: return 1; break; 4 default: return 0; 5 } 6 } cc1plus: warnings being treated as errors t.cc: In function ‘int foo(int)’: t.cc:6: error: control reaches end of non-void function (in 4.4.3)
next prev parent reply other threads:[~2011-02-23 23:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20681-4@http.gcc.gnu.org/bugzilla/> 2011-02-23 22:13 ` pinskia at gcc dot gnu.org 2011-02-24 0:59 ` ami at fischman dot org [this message] 2011-06-27 13:45 ` [Bug c++/20681] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org 2011-11-15 14:20 ` [Bug c++/20681] [4.4/4.5/4.6/4.7 " dimhen at gmail dot com 2011-11-15 15:21 ` redi at gcc dot gnu.org 2011-11-16 9:28 ` dimhen at gmail dot com 2012-01-13 19:48 ` jason at gcc dot gnu.org 2012-01-13 20:20 ` jason at gcc dot gnu.org 2012-01-13 20:22 ` [Bug c++/20681] [4.4/4.5/4.6 " jason at gcc dot gnu.org 2012-03-13 13:41 ` [Bug c++/20681] [4.5/4.6 " jakub at gcc dot gnu.org 2012-07-02 13:34 ` [Bug c++/20681] [4.6 " rguenth at gcc dot gnu.org 2012-10-15 23:53 ` paolo.carlini at oracle dot com [not found] <bug-20681-9121@http.gcc.gnu.org/bugzilla/> 2010-05-22 18:13 ` [Bug c++/20681] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org 2010-09-03 4:53 ` pinskia at gcc dot gnu 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-20681-4-lSZNfFIkLj@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).