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++/50012] [4.6 Regression] C++ front end misses -Wsign-compare warnings when extraneous parentheses are present
Date: Tue, 13 Nov 2012 11:24:00 -0000	[thread overview]
Message-ID: <bug-50012-4-KXsHfCZ5bE@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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|ian at airs dot com, ian at |
                   |gcc dot gnu.org             |
         Resolution|                            |FIXED

--- Comment #11 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-11-13 11:23:58 UTC ---
Fixed.


      parent reply	other threads:[~2012-11-13 11:24 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
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 ` paolo.carlini at oracle dot com [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-50012-4-KXsHfCZ5bE@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: link
Be 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).