From: Alexandre Oliva <oliva@adacore.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org, RTEMS <devel@rtems.org>
Subject: Re: [PATCH] libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep
Date: Thu, 23 Jun 2022 08:33:26 -0300 [thread overview]
Message-ID: <oredzf4nsp.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <e5340839-0fb1-4c3c-5a2f-44dfae57b20a@embedded-brains.de> (Sebastian Huber's message of "Thu, 23 Jun 2022 09:27:44 +0200")
On Jun 23, 2022, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote:
> On 23/06/2022 08:44, Sebastian Huber wrote:
>> http://devel.rtems.org/ticket/4669
Thanks!
> This problem should be fixed now in the RTEMS master branch.
Double thanks! I've applied the patch, and I haven't seen the fails any
more. It's a little too soon to confirm it fixed, but the patch makes
plenty of sense.
> I had to adjust the test case so that it works in a system with only
> one processor:
*nod*, I ran into that myself, and IIRC I've pushed an equivalent fix
earlier this week.
Anyway... I was considering this xfail patch before, and I wonder if it
would still be appropriate to install something like it, narrowed down
to rtems < 6.1, or if it would be better to let it fail noisily so that
people look it up, find the fix proper and merge it.
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/this_thread tests that have detected too-early wakeups to
fail on RTEMS targets.
for libstdc++-v3/ChangeLog
* testsuite/30_threads/this_thread/60421.cc: xfail on RTEMS.
---
.../testsuite/30_threads/this_thread/60421.cc | 1 +
1 file changed, 1 insertion(+)
diff --git a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
index 12dbeba1cc492..4d86e0df20de4 100644
--- a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
+++ b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
@@ -23,6 +23,7 @@
// { dg-require-gthreads "" }
// { dg-require-time "" }
// { dg-require-sleep "" }
+// { dg-xfail-if "nanosleep may wake up too early" { *-*-rtems* } }
#include <thread>
#include <chrono>
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2022-06-23 11:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 6:01 Alexandre Oliva
2022-06-22 6:22 ` Sebastian Huber
2022-06-22 8:55 ` Sebastian Huber
2022-06-23 0:15 ` Alexandre Oliva
2022-06-23 0:19 ` Alexandre Oliva
2022-06-23 6:44 ` Sebastian Huber
2022-06-23 7:27 ` Sebastian Huber
2022-06-23 11:33 ` Alexandre Oliva [this message]
2022-06-23 11:37 ` Sebastian Huber
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=oredzf4nsp.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=devel@rtems.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=sebastian.huber@embedded-brains.de \
/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: 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).