public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46476] New: Missing Warning about unreachable code after return Date: Sun, 14 Nov 2010 17:13:00 -0000 [thread overview] Message-ID: <bug-46476-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46476 Summary: Missing Warning about unreachable code after return Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: paolo.carlini@oracle.com It seems impossible to me that this issue has not been discussed already, but in the library I fixed only two weeks ago a *very* stupid bug which went unnoticed for *many* months exactly because of this. Couldn't believe that GCC didn't warn even at -Wall -Wextra (and -O2). Thus: int foo(int& num) { return num; ++num; // Warn! } int bar(int num) { return num; ++num; // Warn! return num; } For the record, ICC *does* warn, with -Wall.
next reply other threads:[~2010-11-14 16:56 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-14 17:13 paolo.carlini at oracle dot com [this message] 2010-11-14 17:44 ` [Bug c++/46476] " rguenth at gcc dot gnu.org 2012-05-12 14:05 ` manu at gcc dot gnu.org 2014-02-25 9:10 ` stefan at schweter dot it 2021-10-26 12:48 ` [Bug c++/46476] Missing Warning about unreachable code after return [-Wunreachable-code-return] rguenth at gcc dot gnu.org 2021-11-24 15:23 ` rguenth at gcc dot gnu.org 2021-11-25 12:06 ` tschwinge at gcc dot gnu.org 2021-11-26 8:45 ` rguenth at gcc dot gnu.org 2021-11-26 8:45 ` rguenth at gcc dot gnu.org 2021-11-26 8:47 ` rguenth at gcc dot gnu.org 2021-11-26 8:50 ` rguenth at gcc dot gnu.org 2021-11-26 9:48 ` tschwinge at gcc dot gnu.org 2021-11-26 10:04 ` rguenth at gcc dot gnu.org 2021-11-26 10:13 ` rguenth at gcc dot gnu.org 2021-11-26 12:05 ` rguenth at gcc dot gnu.org 2021-11-29 7:21 ` rguenth at gcc dot gnu.org 2021-11-29 13:30 ` rguenth at gcc dot gnu.org 2021-11-29 14:29 ` rguenth at gcc dot gnu.org 2022-07-27 16:58 ` pinskia 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-46476-4@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).