Re: [PATCH/RFC] Enable java on sh64-linux

[Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>]

Tom Tromey <tromey@redhat.com> wrote:
>>> 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.

Thanks.  I'd like to wait comments for libffi and toplevel configury
part.

>>> 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?

Looking closely the Array_3 testcase, I've found that the problematic
try block has only one instruction:

.LEHB1:
	ld.l	r1, 4, r1
.LEHE1:

and if I insert an additional java code after the code which generates
SEGV in the try block, the error goes away.  It looks there is something
wrong in judging whether PC is in the try block or not.  I'll see what
happens in detail.  Thanks for your suggestion.

>>> 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.

I'll try it.
 
> The other test failures don't remind me immediately of problems,
> though the pr83 test was recently discussed on the gcj list.

Ah, I see.  Then except many gij failures, it seems to me that
the Array_3 failure is most problematic.  I believe that the errors
on Process_2 and Thread* come from pthread problems on my target.

Regards,
	kaz