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++] Use __gthread_join in jthread/95989
Date: Thu, 16 Feb 2023 11:12:30 +0000 (GMT)	[thread overview]
Message-ID: <20230216111230.88E9A3857803@sourceware.org> (raw)

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

commit f41840b0354ccffdf31e60080f49c9f5bcc6dc77
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Feb 16 05:54:44 2023 -0300

    [libstdc++] Use __gthread_join in jthread/95989
    
    Bernd Edlinger <bernd.edlinger@hotmail.de> reported that the 95989.cc
    test fails without pthread_join at the end of main, but pthread_join
    is no good for a test that doesn't require pthreads.
    
    This patch adds a __gthread_join call instead.
    
    
    for  libstdc++-v3/ChangeLog
    
            * testsuite/30_threads/jthread/95989.cc (main): Call
            __gthread_join at the end.

Diff:
---
 libstdc++-v3/testsuite/30_threads/jthread/95989.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libstdc++-v3/testsuite/30_threads/jthread/95989.cc b/libstdc++-v3/testsuite/30_threads/jthread/95989.cc
index e98836d0945..407b5274843 100644
--- a/libstdc++-v3/testsuite/30_threads/jthread/95989.cc
+++ b/libstdc++-v3/testsuite/30_threads/jthread/95989.cc
@@ -52,4 +52,5 @@ main()
   test01();
   test02();
   test03();
+  __gthread_join(0, NULL);
 }

                 reply	other threads:[~2023-02-16 11:12 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=20230216111230.88E9A3857803@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).