This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[PATCH, v3] Bringing <mutex> and <condition_variable> up to spec.

From: "Chris Fairles" <chris dot fairles at gmail dot com>
To: gcc-patches at gcc dot gnu dot org, libstdc++ <libstdc++ at gcc dot gnu dot org>
Cc: "Paolo Carlini" <PAOLO dot CARLINI at oracle dot com>, "Benjamin Kosnik" <bkoz at redhat dot com>
Date: Tue, 22 Jul 2008 18:20:10 -0400
Subject: [PATCH, v3] Bringing <mutex> and <condition_variable> up to spec.

Attached patch brings <mutex> and <condition_variable> up to spec
(n2691 WD) given that <chrono> is now in.

I included stubs for timed_mutex and timed_recursive_mutex but when I
went to attempt a basic implementation I noticed that the gthread API
doesn't include pthread_mutex_timedlock and/or pthread_cond_timedwait
if they're available. Should it?

Other general questions,
Is the thread API in the current working draft stable enough to
complete the implementation?
Are there required additions/changes to backend thread-support code
(like gthreads)?

Chris

Attachment: Changelog_thread.txt
Description: Text document

Attachment: thread_chrono_patch.txt
Description: Text document

Follow-Ups:
- Re: [PATCH, v3] Bringing <mutex> and <condition_variable> up to spec.
  - From: Paolo Carlini
- Re: [PATCH, v3] Bringing <mutex> and <condition_variable> up to spec.
  - From: Benjamin Kosnik

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]