public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51296] New: Several 30_threads tests FAIL on Tru64 UNIX Date: Thu, 24 Nov 2011 18:08:00 -0000 [thread overview] Message-ID: <bug-51296-4@http.gcc.gnu.org/bugzilla/> (raw) 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
next reply other threads:[~2011-11-24 17:55 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-24 18:08 ro at gcc dot gnu.org [this message] 2011-11-24 19:27 ` [Bug libstdc++/51296] " redi at gcc dot gnu.org 2011-11-24 20:30 ` redi at gcc dot gnu.org 2011-11-24 21:37 ` redi at gcc dot gnu.org 2011-11-25 14:13 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-25 14:36 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-25 14:47 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-25 15:17 ` redi at gcc dot gnu.org 2011-11-25 15:18 ` redi at gcc dot gnu.org 2011-11-25 15:21 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-25 15:22 ` redi at gcc dot gnu.org 2011-11-25 16:26 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-26 15:24 ` redi at gcc dot gnu.org 2011-11-26 16:03 ` redi at gcc dot gnu.org 2011-11-28 13:24 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-28 14:35 ` redi at gcc dot gnu.org 2011-11-28 14:40 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-28 15:10 ` redi at gcc dot gnu.org 2012-01-11 16:50 ` redi at gcc dot gnu.org 2012-01-11 17:38 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-11 17:49 ` redi at gcc dot gnu.org 2012-01-12 15:48 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-12 16:16 ` redi at gcc dot gnu.org 2012-01-12 18:18 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-13 10:34 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-13 10:54 ` redi at gcc dot gnu.org 2012-01-16 19:37 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-01-16 19:52 ` redi at gcc dot gnu.org 2012-01-31 12:48 ` ro at gcc dot gnu.org 2012-01-31 20:04 ` redi at gcc dot gnu.org 2012-02-01 10:24 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-02-01 10:59 ` redi at gcc dot gnu.org 2012-02-03 8:50 ` redi at gcc dot gnu.org 2012-02-03 8:52 ` redi at gcc dot gnu.org 2012-02-03 9:48 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-02-03 9:51 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-02-07 9:20 ` redi at gcc dot gnu.org 2012-02-07 9:23 ` redi at gcc dot gnu.org 2012-02-10 17:01 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-02-10 18:11 ` ro at gcc dot gnu.org 2012-02-10 18:14 ` ro at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-51296-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).