public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/17937] Critical ~__pool troubles
Date: Tue, 12 Oct 2004 00:30:00 -0000 [thread overview]
Message-ID: <20041012003014.1335.qmail@sourceware.org> (raw)
In-Reply-To: <20041011172441.17937.pcarlini@suse.de>
------- Additional Comments From bkoz at redhat dot com 2004-10-12 00:30 -------
Subject: Re: Critical ~__pool troubles
>Ok, but as long as we don't use that, let's avoid taking the lock a second
>time in _M_reserve_block, the new calls and so on... I propose to protect
>with macros or #if 0 or whatelse those snippets too.
I'm all for eliminating this if indeed it turns out to be a significant overhead.
However, please give me a bit to finish this stuff up! I'll check in a
fix for this immediate problem, and then please give me a bit of time to
do a round of performance analysis. I'll ping you when I'm done, how about that?
best,
benjamin
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17937
next prev parent reply other threads:[~2004-10-12 0:30 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
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 [this message]
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=20041012003014.1335.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).