------- Comment #7 from dave at hiauly1 dot hia dot nrc dot ca 2006-09-20 23:33 ------- Subject: Re: [4.2 Regression] Timeouts in libstdc++, libjava and libgomp testsuites
> Huh. Dave, is revision 116942M the same as revision 116942? I applied r116954 to 116942. > Of these, 19_diagnostics/23591_thread-1.c is probably the easiest to debug. I'm very busy at the moment, so the earliest I will be able to look at this is the weekend. > Since this is the linux target, and not the hpux target, the code paths for > the > locking code should be the same as for x86/linux. > > x86/s390/s390x/powerpc/powerpc64/ia64 all are using these code paths and look > fine. What's different about hppa? It's still using linuxthreads. Also because of the limitations of the ldcw semaphore instruction in PA 1.1, the atomic lock type is 16 bytes and there is a dynamic alignment calculation to select the aligned 4-byte object to use for the ldcw lock. As a result, there are limitations on copying/moving lock objects that aren't present in other implementations. NPTL is coming but its not quite ready for prime time. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29118
