public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/100655] 'g++.dg/tsan/pthread_cond_clockwait.C' FAILs due to 'pthread_cond_clockwait' missing Date: Tue, 18 May 2021 19:57:37 +0000 [thread overview] Message-ID: <bug-100655-4-C23SsvCAZF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100655-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100655 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- It's not glibc-specific though, it's going to be in the next POSIX standard and other C libraries. It's a bit of a hack, but you could include any libstdc++ header and then check _GLIBCXX_USE_PTHREAD_COND_CLOCKWAIT (because libstdc++ already has autoconf checks for it).
next prev parent reply other threads:[~2021-05-18 19:57 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-18 16:36 [Bug testsuite/100655] New: " tschwinge at gcc dot gnu.org 2021-05-18 17:41 ` [Bug testsuite/100655] " kingoipo at gmail dot com 2021-05-18 19:57 ` redi at gcc dot gnu.org [this message] 2021-05-19 7:55 ` rguenth at gcc dot gnu.org 2021-05-19 13:27 ` marxin at gcc dot gnu.org 2021-05-19 14:07 ` redi at gcc dot gnu.org 2021-05-20 9:56 ` redi at gcc dot gnu.org 2021-05-20 12:58 ` redi at gcc dot gnu.org 2021-05-20 18:50 ` bernd.edlinger at hotmail dot de 2021-11-11 20:12 ` msebor at gcc dot gnu.org 2023-11-27 9:33 ` tschwinge at gcc dot gnu.org
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=bug-100655-4-C23SsvCAZF@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).