pthread_mutex_timedlock on sparc64

[Kris Kennaway]

On Wed, Apr 19, 2006 at 08:37:17AM -0400, Daniel Eischen wrote:
> On Wed, 19 Apr 2006, Kris Kennaway wrote:
> 
> >On Wed, Apr 19, 2006 at 03:32:18PM +1000, Sean Winn wrote:
> >>Kris Kennaway wrote:
> >>>On Tue, Apr 18, 2006 at 07:28:00PM +1000, Sean Winn wrote:
> >>>>owner-freebsd-sparc64 at freebsd.org wrote:
> >>>>>
> >>>>>libthr *is* the thread library on sparc64; as Daniel says,
> >>>>>libpthread is not ported to sparc64.
> >>>>>
> >>>>>Kris
> >>>>
> >>>>Not yet in 6.x
> >>>>
> >>>>19:25 Tue 18-Apr sean at bloody [~] uname -msr
> >>>>FreeBSD 6.1-RC1 sparc64
> >>>>19:25 Tue 18-Apr sean at bloody [~] ls -l /usr/lib/libpthread.so
> >>>>lrwxrwxrwx  1 root  wheel  9 Apr 17 04:05 /usr/lib/libpthread.so ->
> >>>>libc_r.so
> >>>
> >>>Oops, I forgot about that..although so did David when he removed
> >>>libc_r from 7.0 and broke sparc :-)
> >>>
> >>>So I guess this is a libc_r missing feature.  Probably the solution is
> >>>to use libthr on 6.x too (I don't know if it works well enough on
> >>>5.x).  libthr causes witness panics under load on sparc64 though.
> >>>
> >>>Kris
> >>
> >>Would threading problems be related to sparc64/73413? I've noticed it
> >>sitting idle for a long while, and the test case still core dumps. The
> >>PR it references (sparc64/72998) also is open.
> >
> >Huh, turns out libpthread does exist on sparc, it's just called
> >libkse.  Anyway, since it's not in use the PR wasn't relevant.
> 
> Yeah, I implemented as much as I could for it, but it doesn't
> work.  So it's installed as libkse as a prod for someone to
> finish and test it.

OK, the PRs should just be suspended then.

We need a list of the many unfinished or unimplemented bits of
FreeBSD/sparc :(

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20060419/00a52749/attachment.pgp