https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67294
Bug ID: 67294 Summary: FAIL: 30_threads/*timed_mutex/unlock/2.cc (test for excess errors) on x86_64-apple-darwin14 Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: dominiq at lps dot ens.fr CC: iains at gcc dot gnu.org, redi at gcc dot gnu.org Target Milestone: --- Host: x86_64-apple-darwin14 Target: x86_64-apple-darwin14 Build: x86_64-apple-darwin14 On x86_64-apple-darwin14 I see the following failures FAIL: 30_threads/recursive_timed_mutex/unlock/2.cc (test for excess errors) UNRESOLVED: 30_threads/recursive_timed_mutex/unlock/2.cc compilation failed to produce executable FAIL: 30_threads/timed_mutex/unlock/2.cc (test for excess errors) UNRESOLVED: 30_threads/timed_mutex/unlock/2.cc compilation failed to produce executable The tests have been introduced at revision r226863 and the failures are /opt/gcc/work/libstdc++-v3/testsuite/30_threads/recursive_timed_mutex/unlock/2.cc:28:25: error: 'recursive_timed_mutex' in namespace 'std' does not name a type using mutex_type = std::recursive_timed_mutex; ^ /opt/gcc/work/libstdc++-v3/testsuite/30_threads/recursive_timed_mutex/unlock/2.cc:30:1: error: 'mutex_type' does not name a type mutex_type m; ^ /opt/gcc/work/libstdc++-v3/testsuite/30_threads/recursive_timed_mutex/unlock/2.cc: In function 'void f()': /opt/gcc/work/libstdc++-v3/testsuite/30_threads/recursive_timed_mutex/unlock/2.cc:34:19: error: 'mutex_type' was not declared in this scope std::lock_guard<mutex_type> l(m); ^ /opt/gcc/work/libstdc++-v3/testsuite/30_threads/recursive_timed_mutex/unlock/2.cc:34:29: error: template argument 1 is invalid std::lock_guard<mutex_type> l(m); ^ /opt/gcc/work/libstdc++-v3/testsuite/30_threads/recursive_timed_mutex/unlock/2.cc:34:33: error: 'm' was not declared in this scope std::lock_guard<mutex_type> l(m); ^