On Wed, Dec 7, 2011 at 7:43 PM, Jack Howarth <howa...@bromo.med.uc.edu> wrote: > Currently we are failing... > > FAIL: gcc.dg/simulate-thread/atomic-load-int128.c -O1 -g thread simulation > test > FAIL: gcc.dg/simulate-thread/atomic-load-int128.c -O2 -g thread simulation > test > FAIL: gcc.dg/simulate-thread/atomic-load-int128.c -O3 -g thread simulation > test > FAIL: gcc.dg/simulate-thread/atomic-load-int128.c -Os -g thread simulation > test > > on x86_64-apple-darwin11 due to the 10 second timeout in simulate-thread of > gcc/testsuite/lib/gcc-simulate-thread.exp. Increasing this timeout to 20 > seconds > eliminates the failures (as these test take ~16 seconds on > x86_64-apple-darwin11). > Okay for gcc trunk?
As said elsewhere, this will double the amount of already large logfile in case of failed test. Do we really need such detailed log? Uros.
