Subject: Re: After newlock2 merge: Different pthread behavior for userland programs?
To: None <>
From: Blair Sadewitz <>
List: port-cobalt
Date: 03/23/2007 09:48:09
Those were the same tests that failed for me.
Glad to hear it's been fixed.  Thanks!

I've gotten so used to newlock2 now that I sometimes forget how much
fun using PTHREAD_CONCURRENCY > 1 used to be. ;)

How's audiomp coming along?



Support WFMU-FM: free-form radio for the masses!

"The frivolity and boredom which unsettle the established order, the
vague foreboding of something unknown, these are the heralds of
approaching change.  The gradual crumbling that left unaltered the
face of the whole is cut short by a sunburst which, in one flash,
illuminates the features of the new world."  --G.W.F. Hegel,
_Phenomenology of Spirit_ 5:11