Re: Patch for i386-darwin: test suite results

[Sandro Tolaini <tolaini at libero dot it>]

On 11/mar/2006, at 12:32, Andrew Haley wrote:

> It isn't, no.  All the gij test failures probably mean that libffi
> isn't working.

Ok, I spent the last days fixing libfff, that now passes its  
testsuite. Obviously, the libjava testsuite is now going better:

Test Run By sandro on Thu Mar 16 21:17:12 2006
Native configuration is i686-apple-darwin8.5.2

                === libjava tests ===

Schedule of variations:
    unix

Running target unix
Using /Users/sandro/staging/share/dejagnu/baseboards/unix.exp as  
board description file for target.
Using /Users/sandro/staging/share/dejagnu/config/unix.exp as generic  
interface file for target.
Using /Users/sandro/gcc-4.0.2/libjava/testsuite/config/default.exp as  
tool-and-target-specific interface file.
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.cni/ 
cni.exp ...
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.compile/ 
compile.exp ...
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.jacks/ 
jacks.exp ...
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.jar/ 
jar.exp ...
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.jni/ 
jni.exp ...
FAIL: noclass execution - gij test
FAIL: pr11951 run
FAIL: throwit execution - gij test
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.lang/ 
lang.exp ...
FAIL: ArrayStore execution - gij test
FAIL: ArrayStore execution - gij test
FAIL: Array_3 execution - gij test
FAIL: Array_3 execution - gij test
FAIL: FileHandleGcTest execution - gij test
FAIL: FileHandleGcTest execution - gij test
FAIL: PR218 execution - gij test
FAIL: PR218 execution - gij test
FAIL: Process_5 execution - gij test
FAIL: Process_5 execution - gij test
FAIL: Process_6 execution - gij test
FAIL: Process_6 execution - gij test
FAIL: StringBuffer_1 execution - gij test
FAIL: StringBuffer_1 execution - gij test
FAIL: StringBuffer_overflow execution - gij test
FAIL: StringBuffer_overflow execution - gij test
FAIL: String_overflow execution - gij test
FAIL: String_overflow execution - gij test
FAIL: Thread_Alive execution - gij test
FAIL: Thread_Alive execution - gij test
FAIL: Thread_Interrupt execution - gij test
FAIL: Thread_Interrupt execution - gij test
FAIL: Thread_Wait_2 execution - gij test
FAIL: Thread_Wait_2 execution - gij test
FAIL: Thread_Wait_Interrupt execution - gij test
FAIL: Thread_Wait_Interrupt 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 -O3 execution - source compiled test
FAIL: Throw_2 execution - gij test
FAIL: Throw_2 -O3 execution - bytecode->native test
FAIL: instinit2 execution - gij test
FAIL: instinit2 execution - gij test
FAIL: invokethrow execution - source compiled test
FAIL: invokethrow execution - gij test
FAIL: invokethrow execution - bytecode->native test
FAIL: invokethrow -O3 execution - source compiled test
FAIL: invokethrow execution - gij test
FAIL: invokethrow -O3 execution - bytecode->native test
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.loader/ 
loader.exp ...
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.mauve/ 
mauve.exp ...
Running /Users/sandro/gcc-4.0.2/libjava/testsuite/libjava.verify/ 
verify.exp ...

                === libjava Summary ===

# of expected passes            3727
# of unexpected failures        43
# of expected failures          14
# of untested testcases         59

Some tests still fail, but in the next days I don't have time to look  
into them further. I'm attaching the patch for who wants to dig into  
it. Note that currently can_unwind_signal=no for this platform. About  
the patch:

* It's based on gcc 4.0.2, but should apply cleanly to 4.0.3 and  
maybe 4.1.0. Will not apply as-is to 4.2, because the damned libffi  
changed quite a bit (there are more parts written in assembly that  
will require porting/tweaking).

* A large part of the patch is to upgrade boehm to a later version.  
If you want, you can import boehm a recent boehm 6.7 or 7.0, that  
supports Darwin/i386. If you apply the patch as-is, you will get the  
boehm-gc that sits currently on the gcc trunk, plus a couple of  
patches to support Darwin/i386.

Many thanks goes to Eric Albert for his help with the Darwin/i386 ABI.

Cheers,
  Sandro

Attachment: gcc-4.0.2-osx.diff
Description: Binary data