public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50012] [4.5/4.6/4.7 Regression] C++ front end misses -Wsign-compare warnings when extraneous parentheses are present Date: Sat, 07 Jan 2012 01:32:00 -0000 [thread overview] Message-ID: <bug-50012-4-CUysGtqlbG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50012-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50012 --- Comment #7 from Ian Lance Taylor <ian at airs dot com> 2012-01-07 01:31:36 UTC --- Created attachment 26260 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26260 Possible patch I did not like the first approach because I think that checking c_dialect_cxx in the generic C family code is quite ugly. But clearly the current approach is problematic, and it's actually easy to implement Richi's suggestion. This patch is a possible approach, but it doesn't work as is. It issues a warning for if (TYPE_QUALS (type) == memfn_quals) in cp;typeck.c. Here memfn_quals is signed int but TYPE_QUALS, an expression of enum values winds up unsigned.
next prev parent reply other threads:[~2012-01-07 1:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-07 11:22 [Bug c++/50012] New: " mikpe at it dot uu.se 2011-08-07 19:52 ` [Bug c++/50012] " mikpe at it dot uu.se 2011-08-08 10:09 ` [Bug c++/50012] [4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org 2011-08-14 12:43 ` mikpe at it dot uu.se 2011-08-19 7:34 ` jakub at gcc dot gnu.org 2011-10-10 12:19 ` rguenth at gcc dot gnu.org 2011-12-19 15:00 ` jakub at gcc dot gnu.org 2012-01-05 17:43 ` jakub at gcc dot gnu.org 2012-01-07 1:32 ` ian at airs dot com [this message] 2012-01-14 0:26 ` ian at gcc dot gnu.org 2012-01-14 0:27 ` [Bug c++/50012] [4.5/4.6 " ian at airs dot com 2012-07-02 12:07 ` rguenth at gcc dot gnu.org 2012-11-13 11:24 ` [Bug c++/50012] [4.6 " 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-50012-4-CUysGtqlbG@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).