public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/53131] -Wlogical-op: ready for prime time in -Wall ? Date: Sat, 28 Apr 2012 10:37:00 -0000 [thread overview] Message-ID: <bug-53131-4-LA51OGL8TP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53131-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53131 --- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-28 10:37:04 UTC --- (In reply to comment #2) > > > > Do the warnings indicate bugs or not? > > Yes. I checked the first ten. And what do the kernel people say? Do they want Wlogical-op enabled? > > There is also PR43772, which would be nice to fix before enabling this in -Wall > > or -Wextra. However, I don't even have any idea why we are warning there. > > Agreed, although I wouldn't regard one broken corner case as a show stopper. > Unfortunately, this corner case triggers in Emacs, so I guess it is not that uncommon. My intention is to try to fix it before touching the status of -Wlogical-op. This will make easier to convince GCC maintainers. However, I have a long list of other things I would like to fix firstm and very little free time, so if you (or anyone else) managed to find out why that bug triggers, it would help already a lot.
next prev parent reply other threads:[~2012-04-28 10:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-26 20:18 [Bug c/53131] New: " dcb314 at hotmail dot com 2012-04-26 21:59 ` [Bug c/53131] " manu at gcc dot gnu.org 2012-04-28 7:30 ` dcb314 at hotmail dot com 2012-04-28 10:37 ` manu at gcc dot gnu.org [this message] 2012-04-28 12:05 ` marc.glisse at normalesup dot org 2012-04-28 12:18 ` dcb314 at hotmail dot com 2012-04-28 12:45 ` marc.glisse at normalesup dot org 2012-05-07 13:45 ` manu at gcc dot gnu.org 2015-04-23 9:49 ` mpolacek 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-53131-4-LA51OGL8TP@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).