public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/12668] Strange warnings with -O1 -Wunreachable-code in 3.3.1,3.3.2,3.4 Date: Sat, 18 Oct 2003 04:29:00 -0000 [thread overview] Message-ID: <20031018042523.13233.qmail@sources.redhat.com> (raw) In-Reply-To: <20031018040741.12668.rmerkert@alphatech.com> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12668 pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |diagnostic Last reconfirmed|0000-00-00 00:00:00 |2003-10-18 04:25:22 date| | ------- Additional Comments From pinskia at gcc dot gnu dot org 2003-10-18 04:25 ------- -O1 enables inlining so that foo is inlined and the warning is right when x is always 0 because that line is never executed in the line version. What is wrong is when you enable line 10, it says that line 2 is never executed twice. It should never tell you that line 2 is not executed at all (because there is no code assocated with it).
next prev parent reply other threads:[~2003-10-18 4:25 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-18 4:25 [Bug c++/12668] New: " rmerkert at alphatech dot com 2003-10-18 4:29 ` pinskia at gcc dot gnu dot org [this message] 2003-10-18 13:51 ` [Bug c++/12668] " rmerkert at alphatech dot com 2003-10-18 14:05 ` rmerkert at alphatech dot com 2003-10-18 19:47 ` pinskia at gcc dot gnu dot org 2003-12-06 9:44 ` [Bug optimization/12668] " pinskia at gcc dot gnu dot org 2004-04-08 13:00 ` 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=20031018042523.13233.qmail@sources.redhat.com \ --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).