public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Fix std::jthread assertion and re-enable skipped test
Date: Wed, 19 May 2021 14:27:23 +0100	[thread overview]
Message-ID: <YKUSO3f5iXzXOupF@redhat.com> (raw)
In-Reply-To: <AM8PR10MB4708B603ADC148D34AB3E7A9E42C9@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM>

On 18/05/21 13:58 +0200, Bernd Edlinger wrote:
>On 5/18/21 1:55 PM, Bernd Edlinger wrote:
>> On 5/17/21 7:13 PM, Jonathan Wakely via Gcc-patches wrote:
>>> libstdc++-v3/ChangeLog:
>>>
>>> 	* include/std/thread (jthread::_S_create): Fix static assert
>>> 	message.
>>> 	* testsuite/30_threads/jthread/95989.cc: Re-enable test.
>>> 	* testsuite/30_threads/jthread/jthread.cc: Do not require
>>> 	pthread effective target.
>>> 	* testsuite/30_threads/jthread/2.cc: Moved to...
>>> 	* testsuite/30_threads/jthread/version.cc: ...here.
>>>
>>> Tested powerpc64le-linux. Committed to trunk.
>>>
>>> Let's see if this test is actually fixed, or if it still causes
>>> failures on some targets.
>>>
>>>
>>
>> Yes, indeed it is failing on x86_64-pc-linux-gnu.
>>
>
>that means only this one:
>
>FAIL: 30_threads/jthread/95989.cc execution test

What's your glibc version?



  reply	other threads:[~2021-05-19 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 17:13 Jonathan Wakely
2021-05-18 11:55 ` Bernd Edlinger
2021-05-18 11:58   ` Bernd Edlinger
2021-05-19 13:27     ` Jonathan Wakely [this message]
2021-05-19 13:37       ` Bernd Edlinger
2021-05-27 12:10         ` Bernd Edlinger

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=YKUSO3f5iXzXOupF@redhat.com \
    --to=jwakely@redhat.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).