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++: testsuite: call sched_yield for nonpreemptive targets
Date: Tue, 21 Jun 2022 00:08:26 +0000 (GMT)	[thread overview]
Message-ID: <20220621000826.40D1138418BE@sourceware.org> (raw)

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

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

    libstdc++: testsuite: call sched_yield for nonpreemptive targets
    
    As in the gcc testsuite, systems without preemptive multi-threading
    require sched_yield calls to be placed at points in which a context
    switch might be needed to enable the test to complete.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/this_thread/60421.cc (test02): Call
            sched_yield.
    
    TN: V608-049

Diff:
---
 libstdc++-v3/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 ad6f9aeffcc..12dbeba1cc4 100644
--- a/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
+++ b/libstdc++-v3/testsuite/30_threads/this_thread/60421.cc
@@ -59,6 +59,7 @@ test02()
   while (!sleeping)
   {
     // Wait for the thread to start sleeping.
+    sched_yield ();
   }
   while (sleeping)
   {


             reply	other threads:[~2022-06-21  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  0:08 Alexandre Oliva [this message]
2022-06-21  0:16 Alexandre Oliva
2022-06-22  0:44 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=20220621000826.40D1138418BE@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: 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).