public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/65704] New: Provide portable versions of std::timed_mutex and std::recursive_timed_mutex
@ 2015-04-08 19:37 redi at gcc dot gnu.org
  2015-04-08 19:37 ` [Bug libstdc++/65704] " redi at gcc dot gnu.org
                   ` (8 more replies)
  0 siblings, 9 replies; 10+ messages in thread
From: redi at gcc dot gnu.org @ 2015-04-08 19:37 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65704

            Bug ID: 65704
           Summary: Provide portable versions of std::timed_mutex and
                    std::recursive_timed_mutex
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org

Currently we don't define std::timed_mutex and std::recursive_timed_mutex
unless the POSIX Timeouts option (_POSIX_TIMEOUTS) is supported. At least
Darwin doesn't support that option.

We should provide portable versions based on a std::mutex and
std::condition_variable::wait_until().


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2015-09-04 16:15 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-08 19:37 [Bug libstdc++/65704] New: Provide portable versions of std::timed_mutex and std::recursive_timed_mutex redi at gcc dot gnu.org
2015-04-08 19:37 ` [Bug libstdc++/65704] " redi at gcc dot gnu.org
2015-04-09 10:17 ` redi at gcc dot gnu.org
2015-04-28 17:38 ` redi at gcc dot gnu.org
2015-09-04 11:24 ` redi at gcc dot gnu.org
2015-09-04 11:24 ` redi at gcc dot gnu.org
2015-09-04 14:17 ` iains at gcc dot gnu.org
2015-09-04 14:24 ` redi at gcc dot gnu.org
2015-09-04 16:09 ` redi at gcc dot gnu.org
2015-09-04 16:15 ` redi at gcc dot gnu.org

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).