public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/36338] heap_sort effectively hangs with -D_GLIBCXX_DEBUG
Date: Tue, 27 May 2008 09:11:00 -0000	[thread overview]
Message-ID: <20080527091018.19251.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36338-9525@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from paolo dot carlini at oracle dot com  2008-05-27 09:10 -------
(In reply to comment #0)

> Looking at pop_heap, it is just a thin wrapper over __pop_heap, along with this
> check. Therefore I believe the easiest fix will be to make sort_heap call
> __pop_heap directly, which avoids the check.

Indeed, makes sense. Will do, thanks for the suggestion.


-- 

paolo dot carlini at oracle dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |paolo dot carlini at oracle
                   |dot org                     |dot com
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-05-27 09:10:18
               date|                            |


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


  reply	other threads:[~2008-05-27  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27  7:36 [Bug libstdc++/36338] New: " chris at bubblescope dot net
2008-05-27  9:11 ` paolo dot carlini at oracle dot com [this message]
2008-05-31 23:02 ` [Bug libstdc++/36338] " paolo at gcc dot gnu dot org
2008-05-31 23:03 ` paolo dot 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=20080527091018.19251.qmail@sourceware.org \
    --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).