public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc(refs/users/aoliva/heads/testme)] libstdc++: testsuite: tolerate non-cancelling sleep
@ 2022-06-23  5:10 Alexandre Oliva
  0 siblings, 0 replies; 4+ messages in thread
From: Alexandre Oliva @ 2022-06-23  5:10 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:f6c91261915c2395a97e75e44279a5531b0d7a45

commit f6c91261915c2395a97e75e44279a5531b0d7a45
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 20:44:07 2022 -0300

    libstdc++: testsuite: tolerate non-cancelling sleep
    
    Though sleep, nanosleep and clock_nanosleep are all POSIX cancellation
    points, not all target systems follow this POSIX requirement.
    30_threads/thread/native_handle/cancel.cc will run until it times out
    on such systems.
    
    Rather than failing a C++ library test because of a limitation of the
    target system, this patch gives the test a chance to successfully
    exercise the features it intends to exercise, by introducing a
    cancellation point in a loop that would otherwise run indefinitely on
    systems exhibiting this limitation.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/thread/native_handle/cancel.cc: Add an
            explicit cancellation point in case sleep_for lacks one.

Diff:
---
 libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc b/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
index dca162b3ace..3cef97e8c53 100644
--- a/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
+++ b/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
@@ -30,7 +30,11 @@ void f(std::atomic<bool>& started)
 {
   started = true;
   while (true)
-    std::this_thread::sleep_for(std::chrono::milliseconds(100));
+    {
+      std::this_thread::sleep_for(std::chrono::milliseconds(100));
+      // In case the target system doesn't make sleep a cancellation point...
+      pthread_testcancel();
+    }
 }
 
 int main()


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [gcc(refs/users/aoliva/heads/testme)] libstdc++: testsuite: tolerate non-cancelling sleep
@ 2022-06-22  5:22 Alexandre Oliva
  0 siblings, 0 replies; 4+ messages in thread
From: Alexandre Oliva @ 2022-06-22  5:22 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:82ea4c64c40b950d38b3808412627cf91f7f67b8

commit 82ea4c64c40b950d38b3808412627cf91f7f67b8
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 20:44:07 2022 -0300

    libstdc++: testsuite: tolerate non-cancelling sleep
    
    Though sleep, nanosleep and clock_nanosleep are all POSIX cancellation
    points, not all target systems follow this POSIX requirement.
    30_threads/thread/native_handle/cancel.cc will run until it times out
    on such systems.
    
    Rather than failing a C++ library test because of a limitation of the
    target system, this patch gives the test a chance to successfully
    exercise the features it intends to exercise, by introducing a
    cancellation point in a loop that would otherwise run indefinitely on
    systems exhibiting this limitation.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/thread/native_handle/cancel.cc: Add an
            explicit cancellation point in case sleep_for lacks one.

Diff:
---
 libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc b/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
index dca162b3ace..3cef97e8c53 100644
--- a/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
+++ b/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
@@ -30,7 +30,11 @@ void f(std::atomic<bool>& started)
 {
   started = true;
   while (true)
-    std::this_thread::sleep_for(std::chrono::milliseconds(100));
+    {
+      std::this_thread::sleep_for(std::chrono::milliseconds(100));
+      // In case the target system doesn't make sleep a cancellation point...
+      pthread_testcancel();
+    }
 }
 
 int main()


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [gcc(refs/users/aoliva/heads/testme)] libstdc++: testsuite: tolerate non-cancelling sleep
@ 2022-06-21  0:17 Alexandre Oliva
  0 siblings, 0 replies; 4+ messages in thread
From: Alexandre Oliva @ 2022-06-21  0:17 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:9a35e3acb54f3ca94aebce144802b553d40883e3

commit 9a35e3acb54f3ca94aebce144802b553d40883e3
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 20:44:07 2022 -0300

    libstdc++: testsuite: tolerate non-cancelling sleep
    
    Though sleep, nanosleep and clock_nanosleep are all POSIX cancellation
    points, not all target systems follow this POSIX requirement.
    30_threads/thread/native_handle/cancel.cc will run until it times out
    on such systems.
    
    Rather than failing a C++ library test because of a limitation of the
    target system, this patch gives the test a chance to successfully
    exercise the features it intends to exercise, by introducing a
    cancellation point in a loop that would otherwise run indefinitely on
    systems exhibiting this limitation.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/thread/native_handle/cancel.cc: Add an
            explicit cancellation point in case sleep_for lacks one.

Diff:
---
 libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc b/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
index dca162b3ace..3cef97e8c53 100644
--- a/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
+++ b/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
@@ -30,7 +30,11 @@ void f(std::atomic<bool>& started)
 {
   started = true;
   while (true)
-    std::this_thread::sleep_for(std::chrono::milliseconds(100));
+    {
+      std::this_thread::sleep_for(std::chrono::milliseconds(100));
+      // In case the target system doesn't make sleep a cancellation point...
+      pthread_testcancel();
+    }
 }
 
 int main()


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [gcc(refs/users/aoliva/heads/testme)] libstdc++: testsuite: tolerate non-cancelling sleep
@ 2022-06-21  0:09 Alexandre Oliva
  0 siblings, 0 replies; 4+ messages in thread
From: Alexandre Oliva @ 2022-06-21  0:09 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:33d2224151a47048e08b0db51a8e718c1889c715

commit 33d2224151a47048e08b0db51a8e718c1889c715
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 20:44:07 2022 -0300

    libstdc++: testsuite: tolerate non-cancelling sleep
    
    Though sleep, nanosleep and clock_nanosleep are all POSIX cancellation
    points, not all target systems follow this POSIX requirement.
    30_threads/thread/native_handle/cancel.cc will run until it times out
    on such systems.
    
    Rather than failing a C++ library test because of a limitation of the
    target system, this patch gives the test a chance to successfully
    exercise the features it intends to exercise, by introducing a
    cancellation point in a loop that would otherwise run indefinitely on
    systems exhibiting this limitation.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/thread/native_handle/cancel.cc: Add an
            explicit cancellation point in case sleep_for lacks one.
    
    TN: V608-051

Diff:
---
 libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc b/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
index dca162b3ace..3cef97e8c53 100644
--- a/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
+++ b/libstdc++-v3/testsuite/30_threads/thread/native_handle/cancel.cc
@@ -30,7 +30,11 @@ void f(std::atomic<bool>& started)
 {
   started = true;
   while (true)
-    std::this_thread::sleep_for(std::chrono::milliseconds(100));
+    {
+      std::this_thread::sleep_for(std::chrono::milliseconds(100));
+      // In case the target system doesn't make sleep a cancellation point...
+      pthread_testcancel();
+    }
 }
 
 int main()


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-06-23  5:10 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-23  5:10 [gcc(refs/users/aoliva/heads/testme)] libstdc++: testsuite: tolerate non-cancelling sleep Alexandre Oliva
  -- strict thread matches above, loose matches on Subject: below --
2022-06-22  5:22 Alexandre Oliva
2022-06-21  0:17 Alexandre Oliva
2022-06-21  0:09 Alexandre Oliva

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).