Currently gcc 4.2.0 suffers from 90 libjava failures on i686-apple-darwin8 including the boehm gctest. Backporting the changes from revision 120684...
http://gcc.gnu.org/viewcvs?view=rev&revision=120684 as suggested in... http://article.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/1416/match=xcode http://article.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/1542/match=xcode reduces the number of failures to 27. The remaining failures in the libjava testsuite are now... WARNING: program timed out. FAIL: Process_5 -O3 execution - bytecode->native test FAIL: StackTrace2 output - gij test FAIL: StackTrace2 output - gij test FAIL: StackTrace2 output - gij test FAIL: StackTrace2 output - gij test FAIL: SyncTest execution - gij test FAIL: SyncTest execution - gij test FAIL: SyncTest execution - gij test FAIL: SyncTest execution - gij test FAIL: Throw_2 execution - source compiled test FAIL: Throw_2 execution - gij test FAIL: Throw_2 execution - bytecode->native test FAIL: Throw_2 execution - gij test FAIL: Throw_2 -findirect-dispatch execution - bytecode->native test FAIL: Throw_2 -O3 execution - source compiled test FAIL: Throw_2 execution - gij test FAIL: Throw_2 -O3 execution - bytecode->native test FAIL: Throw_2 execution - gij test FAIL: Throw_2 -O3 -findirect-dispatch execution - bytecode->native test FAIL: initexc execution - gij test FAIL: initexc execution - gij test FAIL: initexc execution - gij test FAIL: initexc execution - gij test FAIL: stacktrace output - gij test FAIL: stacktrace output - gij test FAIL: stacktrace output - gij test FAIL: stacktrace output - gij test which includes one new failure (Process_5). Shouldn''t the changes in revision 120684 be backported to gcc 4.2.1? Also does anyone know if additional fixes to eliminate these remaining failures currently reside in gcc trunk? Thanks in advance. Jack
