http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51753
--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> 2012-02-10 15:28:17 UTC ---
> With this fixed, all but the
>
> FAIL: gcc.dg/simulate-thread/atomic-load-int128.c -O0 -g thread simulation
> test
>
> failures (at all optimization levels) were gone. I didn't have the
> Linux/x86_64 gcc.log available for comparison, so I still have to
> investigate that one.
With the recent timeout changes, even those failures are gone, so
Solaris/x86 results are clean.
> I'm still seeing a large number of failures both on IRIX 6.5 and Tru64
> UNIX V5.1B (both with gdb 7.4), but I suppose those are better filed as
> separate PRs. I certainly cannot compare gcc.log/g++.log output from
> other OSes since have no machines running e.g. Linux for comparison.
I'll check those with a massively increased timeout to see if that makes
a difference. I wonder if it wouldn't be better to handle those other
platforms in a different PR.
Rainer
