This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
[PATCH/RFC] Enable java on sh64-linux (Take 2)
- From: Andrew Haley <aph at redhat dot com>
- To: Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>
- Cc: java-patches at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, joern dot rennecke at superh dot com, aoliva at redhat dot com
- Date: Thu, 30 Sep 2004 15:48:53 +0100
- Subject: [PATCH/RFC] Enable java on sh64-linux (Take 2)
- References: <20040930.232223.70209832.kkojima@rr.iij4u.or.jp>
Kaz Kojima writes:
> Hi,
>
> SH custom sh-signal.h gets rid of the libjava Array_3 test failure.
> Thanks again for suggestions.
>
> The attached patch is the revised part. New sh-signal.h is also
> used for non SH-5 cpus and MD_FALLBACK_FRAME_STATE_FOR for them
> is changed not to fixup pc there. The patch is tested for non
> SH-5 case with bootstrap and regtests on sh4-unknown-linux-gnu.
>
> Now the result of libjava test for sh64-unknown-linux-gnu is:
These test results are bad.
> FAIL: ArrayStore execution - gij test
> FAIL: ArrayStore execution - gij test
> FAIL: Divide_1 execution - gij test
> FAIL: Divide_1 execution - gij test
This points to a bad divide overflow handler.
> FAIL: FileHandleGcTest execution - gij test
> FAIL: FileHandleGcTest execution - gij test
Don't worry about this one.
> FAIL: LargeFile execution - source compiled test
> FAIL: LargeFile execution - gij test
> FAIL: LargeFile execution - bytecode->native test
> FAIL: LargeFile -O3 execution - source compiled test
> FAIL: LargeFile execution - gij test
> FAIL: LargeFile -O3 execution - bytecode->native test
Or this one.
> FAIL: PR3096 -O3 execution - source compiled test
> FAIL: Process_2 output - source compiled test
> FAIL: Process_2 output - gij test
> FAIL: Process_2 output - bytecode->native test
> FAIL: Process_2 -O3 output - source compiled test
> FAIL: Process_2 output - gij test
> FAIL: Process_2 -O3 output - bytecode->native test
> FAIL: Serialization execution - gij test
> FAIL: Serialization execution - gij test
> FAIL: String_overflow output - gij test
> FAIL: String_overflow output - gij test
> FAIL: Thread_Interrupt execution - gij test
> FAIL: Thread_Interrupt execution - gij test
> FAIL: Thread_Join execution - gij test
> FAIL: Thread_Join execution - gij test
> FAIL: Thread_Wait_2 -O3 execution - source compiled test
> FAIL: Thread_Wait_2 -O3 execution - bytecode->native test
> FAIL: Thread_Wait_Interrupt execution - gij test
> FAIL: Thread_Wait_Interrupt -O3 execution - source compiled test
> FAIL: Thread_Wait_Interrupt execution - gij test
> FAIL: Thread_Wait_Interrupt -O3 execution - bytecode->native test
These are perhaps the thread bugs you mentioned.
> FAIL: negzero execution - gij test
> FAIL: negzero execution - gij test
> FAIL: pr6388 output - gij test
> FAIL: pr6388 output - gij test
These look like weird interpreter bugs. Libffi problems, maybe?
> FAIL: pr83 -O3 output - source compiled test
> FAIL: pr83 -O3 output - bytecode->native test
Not sure about this.
Andrew.