public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aravindvijayan224185 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/51894] New: Fail to warn on likely precedence error in conditional Date: Wed, 18 Jan 2012 20:00:00 -0000 [thread overview] Message-ID: <bug-51894-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51894 Bug #: 51894 Summary: Fail to warn on likely precedence error in conditional Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: aravindvijayan224185@gmail.com Created attachment 26371 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26371 example program showing the failure to warn example program showing the failure to warn: gcc version 4.7.0 If you have: if (ret = return_neg_one() == 1) printf("direct_test==true\n"); else printf("direct_test==false\n"); The compiler will warn: /tmp/tmp.c:51:2: warning: suggest parentheses around assignment used as truth value But if it is a complex conditional: if (!cond || (ret = return_neg_one() == 1)) The compiler will not warn. It seems it should warn in this case as well.
next reply other threads:[~2012-01-18 19:20 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-18 20:00 aravindvijayan224185 at gmail dot com [this message] 2012-01-19 10:31 ` [Bug c/51894] " rguenth at gcc dot gnu.org 2012-01-19 13:59 ` manu 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-51894-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).