Re: new libjava regression on darwin

2006-09-12 Thread Geoffrey Keating
I analysed this problem. It appears that the pthread_cond_timedwait on at least darwin8 sometimes returns a few microseconds early; this may be related to having ntpd running. On darwin9 (and/or darwin8 with -D_APPLE_C_SOURCE defined), sometimes this test hangs, due to a different, known,

Re: new libjava regression on darwin

2006-09-12 Thread Andrew Haley
Geoffrey Keating writes: > > On 11/09/2006, at 3:59 PM, Andrew Pinski wrote: > > >> > >> Geoff, > >>Did you notice that a new libjava regression occured today on > >> Darwin > >> apparently after revision 116838 but by revision 116843? The > >> testcase... > >> > >> FAIL: Threa

Re: new libjava regression on darwin

2006-09-11 Thread Geoffrey Keating
On 11/09/2006, at 3:59 PM, Andrew Pinski wrote: Geoff, Did you notice that a new libjava regression occured today on Darwin apparently after revision 116838 but by revision 116843? The testcase... FAIL: Thread_Sleep -O3 -findirect-dispatch output - bytecode- >native test now fails.

Re: new libjava regression on darwin

2006-09-11 Thread Andrew Pinski
> > Geoff, >Did you notice that a new libjava regression occured today on Darwin > apparently after revision 116838 but by revision 116843? The testcase... > > FAIL: Thread_Sleep -O3 -findirect-dispatch output - bytecode->native test > > now fails. Could this be related to your change... Th

Re: new libjava regression on darwin

2006-09-11 Thread Geoffrey Keating
On 11/09/2006, at 3:51 PM, Jack Howarth wrote: Geoff, Did you notice that a new libjava regression occured today on Darwin apparently after revision 116838 but by revision 116843? The testcase... FAIL: Thread_Sleep -O3 -findirect-dispatch output - bytecode- >native test now fails. C

new libjava regression on darwin

2006-09-11 Thread Jack Howarth
Geoff, Did you notice that a new libjava regression occured today on Darwin apparently after revision 116838 but by revision 116843? The testcase... FAIL: Thread_Sleep -O3 -findirect-dispatch output - bytecode->native test now fails. Could this be related to your change... ---