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: Paolo Carlini <paolo dot carlini at oracle dot com>
To: Chris Fairles <chris dot fairles at gmail dot com>
Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 03 Sep 2008 00:09:33 +0200
Subject: Re: [v3] c++0x <mutex> and <condition_variable>
References: <fac6bb500809021438h329d7137n61bb77da160e7f27@mail.gmail.com> <48BDB75E.1060202@oracle.com> <48BDB90A.6010106@oracle.com>

Paolo Carlini wrote:

Paolo Carlini wrote:
+ in case the test relies on the new gthread support, we need a new dg-require very similar to the one I added for the atomic builtins (look for check_v3_target_atomic_builtins) checking that <bits/c++config.h> defines _GLIBCXX_HAS_GTHREADS. Likewise for any other feature required for the correct build and run of the test (__GTHREAD_HAS_COND?!?). Really rather mechanical additions.
Also, careful with int64_t, must be protected by the dg-require-cstdint...

And remember that the whole <chrono> itself essentially doesn't exist if _GLIBCXX_USE_C99_STDINT_TR1 is undefined. Thus careful not just including it and using its facilities...

Paolo.

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

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

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