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++/36270] A problem with STL map/vector/list whose key is a string in multi-threaded application
Date: Tue, 27 May 2008 09:03:00 -0000 [thread overview]
Message-ID: <20080527090256.3926.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36270-16195@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from paolo dot carlini at oracle dot com 2008-05-27 09:02 -------
(In reply to comment #2)
> Thanks for your quick reply.
> I have upgraded gcc's version to 4.0.2 and the problem is no longer reproduced.
Good. Therefore, I think we can safely close this issue.
> Nonetheless, there is something in your comment that was not quite clear to me.
> You've mentioned that I'm using mt_alloc instead of a default allocator. I'm
> not sure where did I make the choice to use it: there is nothing in the code
> that specifies which allocator to use (I assumed that in this case the default
> will be used). Is it the result of the way the compiler was configured?
Right. For some reason, your distro changed the default for that release.
--
paolo dot carlini at oracle dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |WORKSFORME
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36270
prev parent reply other threads:[~2008-05-27 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 7:30 [Bug libstdc++/36270] New: A problem with STL map/vector/list whose key is a STL " sveta dot cher at gmail dot com
2008-05-20 9:18 ` [Bug libstdc++/36270] A problem with STL map/vector/list whose key is a " paolo dot carlini at oracle dot com
2008-05-27 7:40 ` sveta dot cher at gmail dot com
2008-05-27 9:03 ` paolo dot carlini at oracle dot com [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=20080527090256.3926.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).