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]

Re: [v3] c++0x <mutex> and <condition_variable>

From: "Chris Fairles" <chris dot fairles at gmail dot com>
To: libstdc++ <libstdc++ at gcc dot gnu dot org>, "GCC Patches" <gcc-patches at gcc dot gnu dot org>
Date: Tue, 2 Sep 2008 17:45:33 -0400
Subject: Re: [v3] c++0x <mutex> and <condition_variable>
References: <fac6bb500809021438h329d7137n61bb77da160e7f27@mail.gmail.com>

On Tue, Sep 2, 2008 at 5:38 PM, Chris Fairles <chris.fairles@gmail.com> wrote:
> Ok. I think these are basically ready as a first draft. Nearly
> complete implementations of both. Still missing the generic
> lock/try_lock.
>
> One thing that's unclear to me is how to determine the targets in the
> testcase's dg-do run option. I'm just using what I think Benjamin (or
> whoever did the initial commit) was using. I'm not sure how to go
> about determining whether its still correct or not.
>
> Tested x86_64.
>
> Chris
>

Small fix for unused vars in testcases (for -Wall -O2 testing).

Chris

Attachment: mutex_cond_var_patch.txt
Description: Text document

Follow-Ups:
- Re: [v3] c++0x <mutex> and <condition_variable>
  - From: Chris Fairles

References:
- [v3] c++0x <mutex> and <condition_variable>
  - From: Chris Fairles

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