This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/29496] _M_invalidate function is not thread-safe in GLIBCXX_DEBUG mode
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Oct 2006 11:49:05 -0000
- Subject: [Bug libstdc++/29496] _M_invalidate function is not thread-safe in GLIBCXX_DEBUG mode
- References: <bug-29496-9884@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #11 from pcarlini at suse dot de 2006-10-31 11:49 -------
(In reply to comment #10)
> ... that said, if we don't care *at all* about performance, fixing MT-safety
> bugs in the _Safe_sequence or _Safe_iterator functions it's easy,...
Of course I meant _Safe_sequence_base and _Safe_iterator_base, humpf.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29496