I'm guessing that is dependent on the version of gcc; I've hit this
problem with gcc on Linux, on various versions up to and including gcc
4.1.something. Do you know when specifically this was fixed in gcc?
On Wed, Aug 3, 2011 at 12:32 AM,
On Tue, 02 Aug 2011 19:07:44 +0200, Oliver Seiler
wrote: I've generally found that using function-level static with multiple threads is a Bad Idea (including with Boost.Threads) as the object won't get initialized until the function is run for the "first" time, but this initialization isn't generally thread-safe.
Just a remark: with gcc it is thread-safe
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users