This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 31 Jan 2012 15:27:47 +0000
- Subject: [Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2
- Auto-submitted: auto-generated
- References: <bug-51906-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51906
--- Comment #33 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-01-31 15:27:47 UTC ---
Unsurprising. That code only statically-allocates a mutex, doesn't use C++
non-static data member initializers and doesn't use a recursive mutex (from the
info you've given it seems that all the failures relate to recursive mutexes.)