public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r11-8266] libstdc++: Disable tests that fail after atomic wait/notify rewrite
Date: Tue, 20 Apr 2021 14:27:25 +0000 (GMT)	[thread overview]
Message-ID: <20210420142725.E59B1386188A@sourceware.org> (raw)

https://gcc.gnu.org/g:27350b77a92062667427100afb41fa1160642216

commit r11-8266-g27350b77a92062667427100afb41fa1160642216
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Apr 20 15:11:29 2021 +0100

    libstdc++: Disable tests that fail after atomic wait/notify rewrite
    
    These tests are currently failing, but should be analyzed and
    re-enabled.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/30_threads/semaphore/try_acquire_for.cc: Disable
            test for targets not using futexes for semaphores.
            * testsuite/30_threads/semaphore/try_acquire_until.cc: Likewise.
            * testsuite/30_threads/stop_token/stop_callback/destroy.cc:
            Disable for all targets.
    
    (cherry picked from commit 54995d98cc7746da08d317e4eff756d119136c21)

Diff:
---
 libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_for.cc        | 2 ++
 libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_until.cc      | 2 ++
 libstdc++-v3/testsuite/30_threads/stop_token/stop_callback/destroy.cc | 2 ++
 3 files changed, 6 insertions(+)

diff --git a/libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_for.cc b/libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_for.cc
index e7edc9eeef1..248ecb07e56 100644
--- a/libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_for.cc
+++ b/libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_for.cc
@@ -21,6 +21,8 @@
 // { dg-require-gthreads "" }
 // { dg-add-options libatomic }
 
+// { dg-skip-if "FIXME: fails" { ! futex } }
+
 #include <semaphore>
 #include <chrono>
 #include <thread>
diff --git a/libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_until.cc b/libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_until.cc
index 49ba33b4999..eb1351cd2bf 100644
--- a/libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_until.cc
+++ b/libstdc++-v3/testsuite/30_threads/semaphore/try_acquire_until.cc
@@ -21,6 +21,8 @@
 // { dg-additional-options "-pthread" { target pthread } }
 // { dg-add-options libatomic }
 
+// { dg-skip-if "FIXME: fails" { ! futex } }
+
 #include <semaphore>
 #include <chrono>
 #include <thread>
diff --git a/libstdc++-v3/testsuite/30_threads/stop_token/stop_callback/destroy.cc b/libstdc++-v3/testsuite/30_threads/stop_token/stop_callback/destroy.cc
index 061ed448c33..c2cfba027cb 100644
--- a/libstdc++-v3/testsuite/30_threads/stop_token/stop_callback/destroy.cc
+++ b/libstdc++-v3/testsuite/30_threads/stop_token/stop_callback/destroy.cc
@@ -21,6 +21,8 @@
 // { dg-require-effective-target pthread }
 // { dg-require-gthreads "" }
 
+// { dg-skip-if "FIXME: times out" { *-*-* } }
+
 #include <stop_token>
 #include <atomic>
 #include <thread>


                 reply	other threads:[~2021-04-20 14:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210420142725.E59B1386188A@sourceware.org \
    --to=redi@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: 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).