public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] libstdc++: xfail nanosleep tests on rtems Date: Thu, 23 Jun 2022 08:40:04 +0000 (GMT) [thread overview] Message-ID: <20220623084004.0AD953835680@sourceware.org> (raw) https://gcc.gnu.org/g:281bf61e30990de393c411042620948d5eecdaf3 commit 281bf61e30990de393c411042620948d5eecdaf3 Author: Alexandre Oliva <oliva@adacore.com> Date: Thu Jun 23 04:13:06 2022 -0300 libstdc++: xfail nanosleep tests on rtems Since it has been determined that nanosleep may return slightly too early on RTEMS, due to clock resolution differences, expect 30_thread/async tests that have detected too-early wakeups to fail on RTEMS targets. for libstdc++-v3/ChangeLog * testsuite/30_threads/async/async.cc: xfail on RTEMS. TN: V608-048 Diff: --- libstdc++-v3/testsuite/30_threads/async/async.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/libstdc++-v3/testsuite/30_threads/async/async.cc b/libstdc++-v3/testsuite/30_threads/async/async.cc index 38943ff1a9a..e0b731186c4 100644 --- a/libstdc++-v3/testsuite/30_threads/async/async.cc +++ b/libstdc++-v3/testsuite/30_threads/async/async.cc @@ -2,6 +2,7 @@ // { dg-additional-options "-pthread" { target pthread } } // { dg-require-effective-target c++11 } // { dg-require-gthreads "" } +// { dg-xfail-if "nanosleep may wake up too early" { *-*-rtems* } } // Copyright (C) 2010-2022 Free Software Foundation, Inc. //
next reply other threads:[~2022-06-23 8:40 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-23 8:40 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-06-23 9:03 Alexandre Oliva 2022-06-23 9:03 Alexandre Oliva 2022-06-23 8:39 Alexandre Oliva 2022-06-23 7:15 Alexandre Oliva 2022-06-23 7:15 Alexandre Oliva
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=20220623084004.0AD953835680@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).