http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51906

             Bug #: 51906
           Summary: thread lock test failures on darwin11 under Xcode 4.2
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassig...@gcc.gnu.org
        ReportedBy: howa...@nitro.med.uc.edu


Current gcc trunk exhibits a set of libstdc++ testsuite failures on darwin11
when built with Xcode 4.2.1....

WARNING: program timed out.
FAIL: 30_threads/lock/3.cc execution test
FAIL: 30_threads/recursive_mutex/try_lock/1.cc execution test
FAIL: 30_threads/try_lock/3.cc execution test

at both -m32 and -m64. These appear as...

WARNING: program timed out.
FAIL: 30_threads/lock/3.cc execution test

Assertion failed: (b), function main, file
/sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20120117/libstdc++-v3/testsuite/30_threads/recursive_mutex/try_lock/1.cc,
line 39.FAIL: 30_threads/recursive_mutex/try_lock/1.cc execution test

Assertion failed: (result == -1), function main, file
/sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20120117/libstdc++-v3/testsuite/30_threads/try_lock/3.cc,
line 71.
FAIL: 30_threads/try_lock/3.cc execution test

at both -m32 and -m64. Compiler built as...

COLLECT_GCC=gcc-fsf-4.7
COLLECT_LTO_WRAPPER=/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin11.2.0/4.7.0/lto-wrapper
Target: x86_64-apple-darwin11.2.0
Configured with: ../gcc-4.7-20120117/configure --prefix=/sw
--prefix=/sw/lib/gcc4.7 --mandir=/sw/share/man --infodir=/sw/lib/gcc4.7/info
--with-build-config=bootstrap-lto --enable-stage1-languages=c,lto
--enable-languages=c,c++,fortran,lto,objc,obj-c++,java --with-gmp=/sw
--with-libiconv-prefix=/sw --with-ppl=/sw --with-cloog=/sw --with-mpc=/sw
--with-system-zlib --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
--program-suffix=-fsf-4.7 --enable-checking=yes --enable-cloog-backend=isl
Thread model: posix
gcc version 4.7.0 20120117 (experimental) (GCC)

Reply via email to