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

[Chris Fairles]

On Tue, Jul 29, 2008 at 1:21 PM, Benjamin Kosnik <bkoz@redhat.com> wrote:
>
>> Just want to check if I'm on the right track with the gthread backend
>> modifications (see attached patch for changes). I'm trying not to
>> touch too much objc stuff because I'm not at all familiar with it.
>
> This looks like  you are on the right track to me.
>
> ;)
>
>> One question about _POSIX_TIMEOUTS. The *timedlock's are available if
>> its defined, in the gthr-single, should the wrapper return -1
>> indicating its not supported or should there be no def'n at all? (Same
>> sort of question for gthr-posix.c although there I just don't define
>> the stub w/p _POSIX_TIMEOUTS).
>
> I think no definition is probably better than -1.
>
> best,
> -benjamin
>

Attached patches update <mutex> and <condition_variable> along with
additional gthread backend support. The implementations are still not
complete such as the variadic lock/try_lock's but its a lot closer!

Chris
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mutex_cond_var_patch.txt
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20080730/a1aa08f9/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Changelog_thread.txt
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20080730/a1aa08f9/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gthr-patch.txt
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20080730/a1aa08f9/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Changelog_gthr.txt
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20080730/a1aa08f9/attachment-0003.txt>