Re: [Boost-bugs] [Boost C++ Libraries] #4345: thread::id and joining problem with cascade of threads

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4345: thread::id and joining problem with cascade of threads
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2010-06-16 08:50:41

#4345: thread::id and joining problem with cascade of threads
----------------------------------------------------------+-----------------
 Reporter:  bartek szurgot <bartosz.szurgot@…>            |       Owner:  anthonyw
     Type:  Bugs                                          |      Status:  new     
Milestone:  Boost 1.43.0                                  |   Component:  thread  
  Version:  Boost 1.43.0                                  |    Severity:  Problem 
 Keywords:                                                |  
----------------------------------------------------------+-----------------

Comment(by bartek szurgot <bartosz.szurgot@…>):

 Replying to [comment:5 anthonyw]:
 > Replying to [comment:3 bartek szurgot <bartosz.szurgot@…>]:
 > > Replying to [comment:1 anonymous]:
 > > > g_count is not protected against race conditions. You should use an
 atomic integer or use a mutext to protect g_count.
 > >
 > > it's true, what you say - the same goes for g_started. i left it this
 way intentionally since i work on x86 where ++x on integer is atomic any
 way and i didn't want to complicate example code any more.
 >
 > ++x is '''not''' atomic on integers, even on x86. See
 http://www.devx.com/cplus/Article/42725


 i've read linked article and run tests, but got different results.
 since this discussion is a bit out of scope of this ticket, please contact
 me directly (bartosz dot szurgot at pwr dot wroc dot pl) so we can proceed
 with this topic.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/4345#comment:7>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.