This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/29496] _M_invalidate function is not thread-safe in GLIBCXX_DEBUG mode



------- Comment #22 from pcarlini at suse dot de  2006-11-01 22:42 -------
Created an attachment (id=12531)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12531&action=view)
All the functions working on a set of _Safe_iterators fixed

In my present understanding *all* the functions belonging to
_Safe_iterator_base, _Safe_iterator, _Safe_sequence_base, and _Safe_sequence
going through a full set of iterators attached to a container are currently
weak wrt the scenario presented in this PR, where _M_detach is called by
iterator destructor. This new draft patch reflects that, consistently. I'm
currently testing it, so far everything seems ok on x86-linux and ia64-linux
four-way.


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]