[Bug libstdc++/51296] New: Several 30_threads tests FAIL on Tru64 UNIX
ro at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Thu Nov 24 18:08:00 GMT 2011
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51296
Bug #: 51296
Summary: Several 30_threads tests FAIL on Tru64 UNIX
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ro@gcc.gnu.org
CC: redi@gcc.gnu.org
Host: alpha-dec-osf5.1b
Target: alpha-dec-osf5.1b
Build: alpha-dec-osf5.1b
Between 20111021 (r180287) and 20111128 (r180617), several 30_threads tests
started to FAIL on Tru64 UNIX:
FAIL: 30_threads/async/async.cc execution test
terminate called after throwing an instance of 'std::system_error'
what(): Invalid argument
FAIL: 30_threads/condition_variable/members/1.cc execution test
Assertion failed: false, file
/vol/gcc/src/hg/trunk/local/libstdc++-v3/testsuite/30_threads/condition_variable/members/1.cc,
line 49
FAIL: 30_threads/condition_variable/members/2.cc execution test
Assertion failed: false, file
/vol/gcc/src/hg/trunk/local/libstdc++-v3/testsuite/30_threads/condition_variable/members/2.cc,
line 49
FAIL: 30_threads/condition_variable_any/members/1.cc execution test
FAIL: 30_threads/condition_variable_any/members/2.cc execution test
FAIL: 30_threads/future/cons/constexpr.cc scan-assembler-not
_ZNSt6futureIvEC2Ev
FAIL: 30_threads/future/cons/constexpr.cc scan-assembler-not
_ZNSt6futureIiEC2Ev
FAIL: 30_threads/lock/1.cc execution test
FAIL: 30_threads/lock/3.cc execution test
FAIL: 30_threads/lock/4.cc execution test
FAIL: 30_threads/mutex/lock/1.cc execution test
FAIL: 30_threads/mutex/try_lock/1.cc execution test
FAIL: 30_threads/mutex/try_lock/2.cc execution test
FAIL: 30_threads/shared_future/cons/constexpr.cc scan-assembler-not
_ZNSt13shared_futureIvEC2Ev
FAIL: 30_threads/shared_future/cons/constexpr.cc scan-assembler-not
_ZNSt13shared_futureIiEC2Ev
FAIL: 30_threads/thread/native_handle/typesizes.cc execution test
FAIL: 30_threads/try_lock/1.cc execution test
FAIL: 30_threads/try_lock/2.cc execution test
FAIL: 30_threads/try_lock/3.cc execution test
FAIL: 30_threads/try_lock/4.cc execution test
FAIL: 30_threads/unique_lock/cons/2.cc execution test
FAIL: 30_threads/unique_lock/cons/4.cc execution test
FAIL: 30_threads/unique_lock/locking/1.cc execution test
FAIL: 30_threads/unique_lock/locking/2.cc execution test
FAIL: 30_threads/unique_lock/modifiers/1.cc execution test
FAIL: 30_threads/unique_lock/modifiers/2.cc execution test
This may be due to this change:
2011-10-22 Jonathan Wakely <jwakely.gcc@gmail.com>
PR libstdc++/50196
* acinclude.m4 (GLIBCXX_HAS_GTHREADS): Don't depend on _POSIX_TIMEOUTS.
* configure: Regenerate.
* include/std/mutex (timed_mutex, recursive_timed_mutex): Define
On this platform, _POSIX_TIMEOUTS is missing in <unistd.h>.
I find that those tests are UNSUPPORTED on the 4.6 branch.
Rainer
More information about the Gcc-bugs
mailing list