This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [PATCH/RFC] Enable java on sh64-linux
- From: Tom Tromey <tromey at redhat dot com>
- To: Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>
- Cc: gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org,joern dot rennecke at superh dot com, aoliva at redhat dot com
- Date: 27 Sep 2004 11:22:19 -0600
- Subject: Re: [PATCH/RFC] Enable java on sh64-linux
- References: <20040927.222949.41643720.kkojima@rr.iij4u.or.jp>
- Reply-to: tromey at redhat dot com
>>>>> ">" == Kaz Kojima <kkojima@rr.iij4u.or.jp> writes:
>> The appended patch is to enable java on sh64-*-linux-gnu target.
>> It only affects sh*-linux* targets anyway, and essentially affects
>> sh64-linux only.
This libjava configury bits look fine. Someone else will have to
comment on the rest.
>> I've got the following results on libjava testsuite for mainline:
These are pretty bad...
>> FAIL: Array_3 execution - source compiled test
>> FAIL: Array_3 execution - gij test
>> FAIL: Array_3 execution - bytecode->native test
>> FAIL: Array_3 -O3 execution - source compiled test
>> FAIL: Array_3 execution - gij test
>> FAIL: Array_3 -O3 execution - bytecode->native test
This suggests that the SEGV -> NullPointerException code is not
working properly. I see this port uses dwarf2-signal.h, so perhaps
MD_FALLBACK_FRAME_STATE_FOR isn't working properly?
>> FAIL: Divide_1 execution - gij test
>> FAIL: Divide_1 execution - gij test
... and perhaps you need -fuse-divide-subroutine? This is also set
in configure.host.
The other test failures don't remind me immediately of problems,
though the pr83 test was recently discussed on the gcj list.
Tom