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 libstdc++/50196] [C++0x] std::thread not available under macos Date: Sat, 22 Oct 2011 21:34:00 -0000 [thread overview] Message-ID: <bug-50196-4-wiW7sl1Bbr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50196-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50196 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-10-22 21:34:28 UTC --- Should be fixed for 4.7 - std::timed_mutex and std::recursive_mutex are still not available, because they require a library function which darwin doesn't provide This commit enables new tests for darwin which currently fail due to PR 50598, I assume they will pass when that's fixed
next prev parent reply other threads:[~2011-10-22 21:34 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-26 15:18 [Bug c++/50196] New: std::thread can not use " watsonsong at foxmail dot com 2011-08-26 16:11 ` [Bug c++/50196] " redi at gcc dot gnu.org 2011-08-27 13:13 ` [Bug libstdc++/50196] [C++0x] std::thread not available " paolo.carlini at oracle dot com 2011-08-27 15:53 ` watsonsong at foxmail dot com 2011-08-27 15:55 ` redi at gcc dot gnu.org 2011-10-06 9:58 ` redi at gcc dot gnu.org 2011-10-08 6:31 ` watsonsong at foxmail dot com 2011-10-15 12:54 ` redi at gcc dot gnu.org 2011-10-21 0:15 ` redi at gcc dot gnu.org 2011-10-22 21:31 ` redi at gcc dot gnu.org 2011-10-22 21:34 ` redi at gcc dot gnu.org [this message] 2011-10-24 19:34 ` redi at gcc dot gnu.org 2012-01-28 19:15 ` howarth at nitro dot med.uc.edu 2012-01-28 19:17 ` redi 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-50196-4-wiW7sl1Bbr@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).