Re: 1.5.25-15: pthread_join deadlocks

2009-11-20 Thread Christopher Faylor
On Fri, Nov 20, 2009 at 09:01:00AM -0500, Charles Wilson wrote: >Ryan Johnson wrote: >> Out of curiosity, how much did removing the racy optimization hurt >> performance? The patch just yanked it completely iirc. An alternative >> might be to have the main thread check for single-thread environment

Re: 1.5.25-15: pthread_join deadlocks

2009-11-20 Thread Charles Wilson
Ryan Johnson wrote: > Out of curiosity, how much did removing the racy optimization hurt > performance? The patch just yanked it completely iirc. An alternative > might be to have the main thread check for single-thread environment > only at acquire time, and then release only if it acquired (the l

Re: Re: 1.5.25-15: pthread_join deadlocks

2009-11-20 Thread Ryan Johnson
Corinna Vinschen wrote: On Nov 19 12:29, Ryan Johnson wrote: Hi all, I'm hitting a deadlock with cygwin pthreads when joining on a short-lived thread -- for me the second such thread creation will almost never return. It looks *exactly* like a problem that others noticed as far back as early

Re: 1.5.25-15: pthread_join deadlocks

2009-11-19 Thread Corinna Vinschen
On Nov 19 12:29, Ryan Johnson wrote: > Hi all, > > I'm hitting a deadlock with cygwin pthreads when joining on a > short-lived thread -- for me the second such thread creation will > almost never return. It looks *exactly* like a problem that others > noticed as far back as early 2005 [0], and fr

1.5.25-15: pthread_join deadlocks

2009-11-19 Thread Ryan Johnson
Hi all, I'm hitting a deadlock with cygwin pthreads when joining on a short-lived thread -- for me the second such thread creation will almost never return. It looks *exactly* like a problem that others noticed as far back as early 2005 [0], and from the output of strace on the test case (be