Boost logo

Boost :

From: Lie-Quan Lee (llee1_at_[hidden])
Date: 2001-04-03 13:49:20


At Tue, 03 Apr 2001 17:32:15 -0000,
William Kempf wrote:
> > I guess that pthreads implementations in most of unix flavor OS ( I
> > checked four OS's, IRIX64-6.5, Solaris-2.7 and Linux-2.2.x ix86/alpha)
> > provided unchecked locking semantics. I donot know if Windows native
> > threads supported unchecked locking semantics or not.
>
> Unless the pthreads implementations you checked support the
> PTHREAD_MUTEX_ERRORCHECK type (I'm guessing they don't, since this is
> a new addition to the standard, but I'm not a pthreads expert so may

HI Bill,

The systems I checked have supported error-checked mutex type.

Solaris 2.7
  PTHREAD_MUTEX_DEFAULT
  PTHREAD_MUTEX_NORMAL
  PTHREAD_MUTEX_ERRORCHECK
  PTHREAD_MUTEX_RECURSIVE

Linux 2.2 i386/alpha
  PTHREAD_MUTEX_FAST_NP
  PTHREAD_MUTEX_ERRORCHECK_NP
  PTHREAD_MUTEX_RECURSIVE_NP

IRIX64-6.5
  PTHREAD_MUTEX_DEFAULT
  PTHREAD_MUTEX_SPINBLOCK_NP
  PTHREAD_MUTEX_NORMAL
  PTHREAD_MUTEX_ERRORCHECK
  PTHREAD_MUTEX_RECURSIVE

PTHREAD_MUTEX_DEFAULT in Solaris is basically unspecified on recursive
locking. PTHREAD_MUTEX_NORMAL and PTHREAD_MUTEX_DEFAULT will dealock
on recursive locking. PTHREAD_MUTEX_ERRORCHECK is the checked mutex.
PTHREAD_MUTEX_RECURSIVE is the recursived one. PTHREAD_MUTEX_FAST_NP
one in Linux behaves the same as PTHREAD_MUTEX_NORMAL.

--
Rich

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk