GCJ/minGW produced executables and linux/wine

[Andrew Haley]

Jeff Sturm writes:
 > 
 > The failures were:
 > 
 > FAIL: Array_3 execution - source compiled test
 > FAIL: Array_3 execution - bytecode->native test
 > FAIL: Array_3 -O execution - source compiled test
 > FAIL: Array_3 -O execution - bytecode->native test
 > FAIL: Divide_1 execution - source compiled test
 > FAIL: Divide_1 execution - bytecode->native test
 > FAIL: Divide_1 -O execution - source compiled test
 > FAIL: Divide_1 -O execution - bytecode->native test
 > FAIL: SyncTest execution - bytecode->native test
 > FAIL: SyncTest -O execution - bytecode->native test
 > FAIL: TestProxy execution - source compiled test
 > FAIL: TestProxy execution - bytecode->native test
 > FAIL: TestProxy -O execution - source compiled test
 > FAIL: TestProxy -O execution - bytecode->native test
 > FAIL: Thread_Interrupt execution - source compiled test
 > FAIL: Thread_Interrupt execution - bytecode->native test
 > FAIL: Thread_Interrupt -O execution - source compiled test
 > FAIL: Thread_Interrupt -O execution - bytecode->native test
 > FAIL: Thread_Wait_2 execution - source compiled test
 > FAIL: Thread_Wait_2 execution - bytecode->native test
 > FAIL: Thread_Wait_2 -O execution - source compiled test
 > FAIL: Thread_Wait_2 -O execution - bytecode->native test
 > FAIL: Thread_Wait_Interrupt output - source compiled test
 > FAIL: Thread_Wait_Interrupt output - bytecode->native test
 > FAIL: Thread_Wait_Interrupt -O output - source compiled test
 > FAIL: Thread_Wait_Interrupt -O output - bytecode->native test
 > FAIL: Throw_2 execution - source compiled test
 > FAIL: Throw_2 execution - bytecode->native test
 > FAIL: Throw_2 -O execution - source compiled test
 > FAIL: Throw_2 -O execution - bytecode->native test

Your exception handling is totally busted.

Andrew.