public inbox for
 help / color / mirror / Atom feed
From: Alexandre Oliva <>
Subject: Re: [PATCH] libstdc++: async: tolerate slightly shorter sleep
Date: Thu, 23 Jun 2022 08:36:21 -0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Alexandre Oliva's message of "Wed, 22 Jun 2022 03:03:15 -0300")

On Jun 22, 2022, Alexandre Oliva <> wrote:

> Regstrapped on x86_64-linux-gnu, also tested with a cross to
> aarch64-rtems6.  Ok to install?

The early wakeups are fixed for rtems6.1, so the same question raised at apply to
this one:

libstdc++: xfail nanosleep tests on rtems

From: Alexandre Oliva <>

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/ xfail on RTEMS.

TN: V608-048
 libstdc++-v3/testsuite/30_threads/async/ |    1 +
 1 file changed, 1 insertion(+)

diff --git a/libstdc++-v3/testsuite/30_threads/async/ b/libstdc++-v3/testsuite/30_threads/async/
index 38943ff1a9a5e..e0b731186c459 100644
--- a/libstdc++-v3/testsuite/30_threads/async/
+++ b/libstdc++-v3/testsuite/30_threads/async/
@@ -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.

Alexandre Oliva, happy hacker      
   Free Software Activist                       GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <>

  reply	other threads:[~2022-06-23 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  6:03 Alexandre Oliva
2022-06-23 11:36 ` Alexandre Oliva [this message]
2022-10-12 11:41   ` Jonathan Wakely
2022-10-12 11:45     ` Jonathan Wakely
2022-10-12 21:11       ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be 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).