This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Current gcj on powerpc
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>, <java at gcc dot gnu dot org>
- Date: Thu, 1 Aug 2002 11:53:12 -0400 (EDT)
- Subject: Re: Current gcj on powerpc
On 31 Jul 2002, Mark Wielaard wrote:
> Embarrassing... But I did test the patch on a x86 machine and it really
> looked innocent. I have no idea why that would cause a simple program
> like the following to fail:
It shouldn't.
> But it seems that it does on powerpc-unknown-linux-gnu. Can anybody spot
> anything in that patch that could cause the whole exception mechanism to
> fail (in exception.cc:110)?
> (And only with shared libraries, compiling with -static works ok.)
Assuming this patch really is responsible, it may not be a DSO vs. -static
thing anyway. The static executable you built may not have linked with
the gnu.java.security objects at all, so would be unaffected by this
patch.
Can you place a breakpoint on abort() and find out what the
_Unwind_Reason_Code is? The comment suggests it could be
_URC_END_OF_STACK or some other failure.
> I am going to double check this by doing a complete clean compile of the
> HEAD with only this patch reversed tonight. If that produces a gcj that
> works correctly on the above program I will reverse the patch and figure
> out later what particular part of the patch caused it.
I'm not sure if it worth reversing; I don't see a failure on sparc, i386
or alpha.
Jeff