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: "howarth at nitro dot med.uc.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 27 Jan 2012 17:36:08 +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 #8 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-01-27 17:36:08 UTC ---
Opened as radr://10765474, "darwin11 linker bug exposed by new libstdc++ thread
tests" although it appears to be more complex than a simple linker bug as...
1) 30_threads/recursive_mutex/try_lock/1.cc compiled under darwin10 runs fine
under darwin11. Also, the darwin10 generated 1.s can be reassembled and
relinked under darwin11 and the resulting 1.exe runs fine.
2) 30_threads/recursive_mutex/try_lock/1.cc compiled under darwin11 using
-mmacosx-version-min=10.6 fails when run under either darwin11 or darwin10.
Using the 1.s generated above to reassemble and relink under darwin10 still
shows the execution failure.