public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jmarronn at rockwellcollins dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14889] New: Bad detection of unreachable code with option -O -Wunreachable-code Date: Thu, 08 Apr 2004 12:53:00 -0000 [thread overview] Message-ID: <20040408125352.14889.jmarronn@rockwellcollins.com> (raw) On cygwin (CYGWIN_NT-5.0) on plateform W2K (5.00.2195) and g++ (gcc version 3.3.1 (cygming special), I have a probleme with option -Wunreachable-code and - O. G++ signal unreach code, which is totaly "reachable"... Compilation sample: $ g++ -O -Wunreachable-code essai.cpp -o essai essai.cpp: In function `int main()': essai.cpp:17: warning: will never be executed Run result: $ ./essai true false Source of essai.cpp #include <iostream> class Condition { public: void EssaiCond( const int ); }; void Condition::EssaiCond( const int cond ) { if(cond) { std::cout << "true\n"; } else { std::cout << "false\n"; } } int main() { Condition essai; essai.EssaiCond(true); essai.EssaiCond(false); return(0); } -- Summary: Bad detection of unreachable code with option -O - Wunreachable-code Product: gcc Version: 3.3.1 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jmarronn at rockwellcollins dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14889
next reply other threads:[~2004-04-08 12:53 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-08 12:53 jmarronn at rockwellcollins dot com [this message] 2004-04-08 13:00 ` [Bug c++/14889] " 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=20040408125352.14889.jmarronn@rockwellcollins.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).