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: Wed, 01 Feb 2012 11:01:12 +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
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2012-02-01
AssignedTo|unassigned at gcc dot |redi at gcc dot gnu.org
|gnu.org |
Target Milestone|--- |4.7.0
Ever Confirmed|0 |1
--- Comment #35 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-01 11:01:12 UTC ---
(In reply to comment #34)
> A recursive mutex using pthread_mutex_init() works.
Thanks for the analysis.
I'm going to add some extra preprocessor conditions around the __mutex_base and
__recursive_mutex_base initialization so that target maintainers can force use
of the pthread_mutex_init function on an OS-by-OS basis. That should allow
this issue to be fixed for Lion and PR 51296 to be fixed for Tru64.