This is the mail archive of the cygwin-developers mailing list for the Cygwin 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: pthread_barrier_* API implementation


On 1 February 2016 at 08:38, Yaakov Selkowitz <yselkowitz@cygwin.com> wrote:
> On 2016-02-01 00:41, VÃclav Haisman wrote:
>>
>> On rakudo.org ([1]) pages, I have noticed that the pthread_barrier_*
>> POSIX API is missing from Cygwin. I took a look at NetBSD and FreeBSD
>> implementations of it. It seemed to me that creating POSIX barrier on
>> top of POSIX mutex and POSIX conditional variable is not that hard ([2]).
>>
>> Now, the question is whether this is acceptable and whether it should be
>> part of Newlib or directly part of Cygwin?
>
>
> IMO a barriers implementation would be welcome.  winsup/cygwin/thread.cc
> would be the place for it.
>
>> Second, if I should pursue that, or if anyone who knows either Newlib or
>> Cygwin better than I wants to mould the source into an acceptable form.
>> I would not mind somebody else doing it. :D
>
>
> PTC. :-)
>
>> I have, in the past, contributed small patches to Cygwin and I had done
>> the necessary copyright assignment paper work, so copyright should not
>> be a problem.
>
>
> That would certainly be a prerequisite.
>
> --
> Yaakov


Well, I tried and I started adding the functions into the thread.cc
file (https://github.com/wilx/newlib-cygwin/commit/bf917b59d644eaac8fb5f72c5060bb44aa044804).
Then I noticed I do not know where to put the necessary structures.
Newlib headers seem to already contain some definitions of
pthread_barrier_t and pthread_barrierattr_t. The organization of the
source escapes me.


-- 
VH


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