https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93599
--- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- (In reply to Thomas Koenig from comment #4) > Created attachment 47800 [details] > Possible fix > > Here is something that Nicolas and I came up with. The theory is that > pthread_cond_wait can get a spurious interrupt once in a blue moon which > previosly led to the macro becoming a no-op. > > I have tested this to around 8 Million invocations of the test program, but > this is not a guarantee... > > Incidentially, this also appears to fix the issue that helgrind reported. > It passes regression testing. > > Is there a reasonable way to test this further? Awesome sleuthing. I think we could run your test case on a PowerPC64 either in the gcc compile farm for at OSU (Oregon State University) I will check to see if I can still get into the OSU machine.
