This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [PATCH] posix gthreads additions for c++0x thread library
- From: "Chris Fairles" <chris dot fairles at gmail dot com>
- To: "Paolo Carlini" <paolo dot carlini at oracle dot com>
- Cc: "GCC Patches" <gcc-patches at gcc dot gnu dot org>, libstdc++ <libstdc++ at gcc dot gnu dot org>, "Mark Mitchell" <mark at codesourcery dot com>
- Date: Mon, 18 Aug 2008 17:58:04 -0400
- Subject: Re: [PATCH] posix gthreads additions for c++0x thread library
- References: <fac6bb500808181334g20d7f748r471bd6825979a337@mail.gmail.com> <48A9E68A.8070101@oracle.com> <48A9E969.8020700@oracle.com> <48A9EB71.4020106@oracle.com> <fac6bb500808181456l46aef0dh26a75e2403f7ed25@mail.gmail.com>
On Mon, Aug 18, 2008 at 5:56 PM, Chris Fairles <chris.fairles@gmail.com> wrote:
> On Mon, Aug 18, 2008 at 5:36 PM, Paolo Carlini <paolo.carlini@oracle.com> wrote:
>> Paolo Carlini wrote:
>>>
>>> In other terms: wouldn't it be possible to prepare an autoconf test
>>> completely similar to [GLIBCXX_ENABLE_THREADS], thus looking inside
>>> $gthread_file with grep. To make things easier could be defined a new
>>> __GTHREADS_CXX0X or something like that?
>>
>> Actually, __GTHREAD_HAS_COND already exists, grepping for something similar,
>> corresponding to the new functionalities seems absolutely doable to me.
>>
>> Paolo.
>>
>
> But is _GTHREAD_HAS_COND alone appropriate? There are other things
> like __gthread_time_t, sched_yield, pthread_self that aren't related
> but are still required. I like the __GTHREADS_CXX0X idea. Simply
> define that in any gthr-*.h header that defines ALL required types and
> functions that the c++0x library uses. Something like the attached
> (untested)?
>
> Chris
>
Forgot to move the check in configure.ac into the "unconditional"
section. That was what I intended.
Chris