public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/17937] Critical ~__pool troubles
Date: Mon, 11 Oct 2004 22:51:00 -0000 [thread overview]
Message-ID: <20041011225149.28342.qmail@sourceware.org> (raw)
In-Reply-To: <20041011172441.17937.pcarlini@suse.de>
------- Additional Comments From bkoz at gcc dot gnu dot org 2004-10-11 22:51 -------
It would be list.... ugh. Damn that allocator rebinding! I'm developing severe
issues with this particular container. Well, this kills off this QoI
improvement. I've reverted this on mainline, and fixed up the testcases that
test for this to be of the type that showed this, more advanced, problem.
I'm going to keep the infrastructure in __mt_alloc to do the actual
deallocations, however. At least, for the time being.
Sorry about this madness.
-benjamin
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2004-10-11 22:51:49
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17937
next prev parent reply other threads:[~2004-10-11 22:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 17:24 [Bug libstdc++/17937] New: " pcarlini at suse dot de
2004-10-11 17:26 ` [Bug libstdc++/17937] " pcarlini at suse dot de
2004-10-11 17:38 ` pcarlini at suse dot de
2004-10-11 22:51 ` bkoz at gcc dot gnu dot org [this message]
2004-10-11 22:52 ` bkoz at gcc dot gnu dot org
2004-10-11 23:50 ` pcarlini at suse dot de
2004-10-12 0:30 ` bkoz at redhat dot com
2004-10-12 1:10 ` cvs-commit at gcc dot gnu dot org
2004-10-12 8:28 ` pcarlini at suse dot de
2004-10-12 8:53 ` pcarlini at suse dot de
2004-10-12 15:50 ` bkoz at gcc dot gnu dot org
2004-10-12 15:54 ` pcarlini at suse dot de
2004-10-13 2:56 ` bkoz at gcc dot gnu dot org
2004-10-13 18:28 ` matz at suse dot de
2004-10-13 18:33 ` pinskia at gcc dot gnu dot org
2004-10-13 18:37 ` matz at suse dot de
2004-10-13 18:39 ` pinskia at gcc dot gnu dot org
2004-10-13 18:41 ` matz at suse dot de
2004-10-13 18:42 ` matz at suse dot de
2004-10-15 17:13 ` pinskia at gcc dot gnu dot 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=20041011225149.28342.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).