Mauve harness failure on s390

Fri Jan 31 15:45:00 GMT 2003

Hoi,
On Fri, 2003年01月31日 at 16:08, Ulrich Weigand wrote:
> What I'm wondering is why this is apparently platform-dependent;
> I'd have thought the compilation to bytecode would be independent
> of the platform, and likewise the question whether any given
> bytecode sequence contains unreachable code or not ...

It isn't platform dependent. I just updated Mauve from CVS and see the
same thing on i686-pc-linux-gnu.
It depends on how gcj uses the Mauve testsuite. The dejagnu test wrapper
fails when it sees unexpected warnings. The unreachable bytecode
warnings should be harmless (although they do indicate that gcj -C
produces non-optimal bytecode). Somehow the libjava_prune_warnings from
libjava/testsuite/lib/libjava.exp isn't working correctly.
> Any suggestions how to debug such problems? Is there something
> like a bytecode disassembler / verifier / analyser tool?

You can use jcf-dump -c to decompile and gcj --syntax-only to verify a
class file.
Cheers,
Mark