public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/62270] -Wlogical-not-parentheses warnings Date: Sat, 06 Sep 2014 08:22:00 -0000 [thread overview] Message-ID: <bug-62270-4-zDnrwve3SH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62270-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62270 --- Comment #10 from Marek Polacek <mpolacek at gcc dot gnu.org> --- (In reply to David Binderman from comment #9) > Is a brand new warning ready for the prime time of -Wall ? The warning existed for some time already before it's been added to -Wall. > It might be a tad more conservative to implement the proposed warning > and not include it in -Wall until some time has elapsed and some user > feedback has been provided. That's what happened. And I believe few people noticed the new warning. > For instance, what effect does new flag -Wlogical-not-parentheses have > on building major packages like the Linux kernel, or Fedora, > or others ? Some of them won't build because of -Werror, I suppose, but that happens every year when we do the mass rebuilds; -Wall isn't guaranteed to be consistent from release to release. It should not have almost any false positives, and there's always the option to use -Wno-logical-not-parentheses or to wrap LHS in parens to suppress the warning.
prev parent reply other threads:[~2014-09-06 8:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-26 17:22 [Bug fortran/62270] New: " mpolacek at gcc dot gnu.org 2014-09-02 7:52 ` [Bug fortran/62270] " burnus at gcc dot gnu.org 2014-09-02 7:58 ` mpolacek at gcc dot gnu.org 2014-09-02 16:08 ` mpolacek at gcc dot gnu.org 2014-09-02 16:09 ` mpolacek at gcc dot gnu.org 2014-09-03 16:05 ` mpolacek at gcc dot gnu.org 2014-09-03 17:26 ` mpolacek at gcc dot gnu.org 2014-09-05 22:17 ` dcb314 at hotmail dot com 2014-09-06 8:22 ` mpolacek at gcc dot gnu.org [this message]
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-62270-4-zDnrwve3SH@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).