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++/53263] priority_queue is very slow if -D_GLIBCXX_DEBUG is used
Date: Wed, 16 Oct 2013 11:13:00 -0000	[thread overview]
Message-ID: <bug-53263-4-le56CROlEq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53263-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.8.1                       |4.7.0
   Target Milestone|---                         |4.8.0

--- Comment #23 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Domink, why did you change the version of this bug on 2013-06-24 (and reopen
it)?

It was reported against 4.7.0, before 4.8.0 was even released, so cannot be a
bug in 4.8.1, right?

I'm restoring the version to 4.7.0 and setting target to 4.8.0 since that's
where the fix appeared.


      parent reply	other threads:[~2013-10-16 11:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 11:48 [Bug libstdc++/53263] New: " dominik.strasser@onespin-solutions.com
2012-05-07 12:06 ` [Bug libstdc++/53263] " paolo.carlini at oracle dot com
2012-05-07 12:07 ` paolo.carlini at oracle dot com
2012-05-07 12:43 ` dominik.strasser@onespin-solutions.com
2012-05-07 12:55 ` paolo.carlini at oracle dot com
2012-05-07 13:37 ` pluto at agmk dot net
2012-05-07 20:51 ` fdumont at gcc dot gnu.org
2012-05-07 21:14 ` paolo.carlini at oracle dot com
2012-05-08  8:07 ` pluto at agmk dot net
2012-05-08  9:56 ` paolo.carlini at oracle dot com
2012-05-08 20:02 ` fdumont at gcc dot gnu.org
2012-05-11 20:20 ` fdumont at gcc dot gnu.org
2012-05-12 21:57 ` paolo.carlini at oracle dot com
2012-05-14 20:20 ` fdumont at gcc dot gnu.org
2012-06-11 15:06 ` dominik.strasser@onespin-solutions.com
2012-06-11 15:27 ` paolo.carlini at oracle dot com
2013-06-24 11:34 ` dominik.strasser@onespin-solutions.com
2013-06-24 11:47 ` dominik.strasser@onespin-solutions.com
2013-06-24 11:51 ` paolo.carlini at oracle dot com
2013-06-24 11:58 ` paolo.carlini at oracle dot com
2013-06-24 12:13 ` dominik.strasser@onespin-solutions.com
2013-06-24 12:17 ` paolo.carlini at oracle dot com
2013-10-16 11:13 ` redi 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-53263-4-le56CROlEq@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).