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++/53158] [C++11] Bogus error in loop condition Date: Mon, 07 May 2012 19:04:00 -0000 [thread overview] Message-ID: <bug-53158-4-utvbOC3bgf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53158-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53158 --- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-05-07 18:38:34 UTC --- void foo(); void bar(int a, int b) { if (foo() && a < b) ; }
next prev parent reply other threads:[~2012-05-07 18:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-29 4:42 [Bug c++/53158] New: " zeratul976 at hotmail dot com 2012-05-07 16:19 ` [Bug c++/53158] " paolo.carlini at oracle dot com 2012-05-07 19:04 ` paolo.carlini at oracle dot com [this message] 2012-05-10 21:15 ` paolo at gcc dot gnu.org 2012-05-10 21:28 ` paolo.carlini at oracle dot com
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-53158-4-utvbOC3bgf@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).