Hi all!
Here is attached a diff of libpipe directory, with code changed to
pthreads.
I have substituted condition_implies function with a pointer trick.
Waiting for some feedback. ;)
There are also some code for checking in
http://es.gnu.org/~zenton/Pthread
Thanks,
Vicente.
PD: Merry Christmas
Hi all!
Sorry for the delay on continuing this thread. ;)
El lun, 02-12-2002 a las 19:25, Marcus Brinkmann escribió:
> On Mon, Dec 02, 2002 at 09:13:20AM -0800, Thomas Bushnell, BSG wrote:
> > Roland McGrath <[EMAIL PROTECTED]> writes:
> >
> > > > We still need a way to keep track of what they
> Right, and like I said, they need a way to keep track of which
> conditions they need to signal.
No, for all the extant users it is already static.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
On Mon, Dec 02, 2002 at 09:13:20AM -0800, Thomas Bushnell, BSG wrote:
> Roland McGrath <[EMAIL PROTECTED]> writes:
>
> > > We still need a way to keep track of what they are, and the existing
> > > mechanism is basically the only way. We can either implement it with
> > > a wrapper around pthread
Roland McGrath <[EMAIL PROTECTED]> writes:
> > We still need a way to keep track of what they are, and the existing
> > mechanism is basically the only way. We can either implement it with
> > a wrapper around pthread conditions, or exted pthread conditions. The
> > latter seems better.
>
> Or,
> We still need a way to keep track of what they are, and the existing
> mechanism is basically the only way. We can either implement it with
> a wrapper around pthread conditions, or exted pthread conditions. The
> latter seems better.
Or, as I suggested, all the users (all four of them) of thi
Roland McGrath <[EMAIL PROTECTED]> writes:
> > We need pthread implementations (as GNU extensions) for them.
>
> I am not convinced we really need it. The caller can just signal several
> conditions. If this were used in more than two places, it could be done
> with a wrapper around lists of co
> We need pthread implementations (as GNU extensions) for them.
I am not convinced we really need it. The caller can just signal several
conditions. If this were used in more than two places, it could be done
with a wrapper around lists of conds. But it's not, so the code could as
easily be cha
On Sun, Dec 01, 2002 at 04:11:05AM +0100, Vicente Hernando Ara wrote:
> When changing cthread code to pthread i have found this problem:
>
> In file hurd/libpipe/pipe.c appear the following functions:
>
> condition_implies and condition_unimplies
>
> What are the best way to change them to pthre
Hi all!
When changing cthread code to pthread i have found this problem:
In file hurd/libpipe/pipe.c appear the following functions:
condition_implies and condition_unimplies
What are the best way to change them to pthread?
form cprocs.c and libpthread/sysdeps/generic/bits/condition.h ... fi
10 matches
Mail list logo
