public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/47662] [4.6 Regression] -fno-operator-names no longer works with STL headers
Date: Thu, 10 Feb 2011 22:51:00 -0000	[thread overview]
Message-ID: <bug-47662-4-F4CpT6mxUi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47662-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47662

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-10 22:43:14 UTC ---
Fixed.

I've just realised I should have put Jakub's name on the new test - sorry about
that!  I haven't checked in a test for -std=gnu++0x mode yet, that will follow
shortly.


  parent reply	other threads:[~2011-02-10 22:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 14:18 [Bug libstdc++/47662] New: " jakub at gcc dot gnu.org
2011-02-09 14:23 ` [Bug libstdc++/47662] " jakub at gcc dot gnu.org
2011-02-09 14:28 ` redi at gcc dot gnu.org
2011-02-09 14:34 ` redi at gcc dot gnu.org
2011-02-09 15:13 ` paolo.carlini at oracle dot com
2011-02-10 10:12 ` jakub at gcc dot gnu.org
2011-02-10 10:25 ` redi at gcc dot gnu.org
2011-02-10 10:54 ` paolo.carlini at oracle dot com
2011-02-10 22:42 ` redi at gcc dot gnu.org
2011-02-10 22:51 ` redi at gcc dot gnu.org [this message]
2011-02-11  0:42 ` paolo.carlini at oracle dot com
2011-02-12 19:07 ` redi 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-47662-4-F4CpT6mxUi@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).