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?
Jack
gcc/testsuite/
2011-12-07 Jack Howarth <howa...@bromo.med.uc.edu>
* lib/gcc-simulate-thread.exp (simulate-thread): Increase timeout
to 20 seconds.
Index: gcc/testsuite/lib/gcc-simulate-thread.exp
===================================================================
--- gcc/testsuite/lib/gcc-simulate-thread.exp (revision 182083)
+++ gcc/testsuite/lib/gcc-simulate-thread.exp (working copy)
@@ -56,8 +56,8 @@ proc simulate-thread { args } {
set gdb_worked 0
- # Set timeout to 10 seconds due to huge amount of generated log.
- remote_expect target 10 {
+ # Set timeout to 20 seconds due to huge amount of generated log.
+ remote_expect target 20 {
# Too old GDB
-re "Unhandled dwarf expression|Error in sourced command file" {
unsupported "$testcase $message"
