This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: Compiler errors while parsing bytecode files.
- To: Bryce McKinlay <bryce at albatross dot co dot nz>
- Subject: Re: Compiler errors while parsing bytecode files.
- From: Tom Tromey <tromey at cygnus dot com>
- Date: Thu, 30 Sep 1999 13:36:15 -0700
- Cc: Andrew Haley <aph at pasanda dot cygnus dot co dot uk>, GChambers at provsol dot com, java-discuss at sourceware dot cygnus dot com
- References: <19990927182058.11108.qmail@pasanda.cygnus.co.uk><37F00186.69C967C1@albatross.co.nz>
>>>>> "Bryce" == Bryce McKinlay <bryce@albatross.co.nz> writes:
Bryce> As a general warning, I've noticed several cases where bytecode
Bryce> produced by Jikes will not compile with gcj, while bytecode
Bryce> produced by javac or "gcj -C" from exactly the same source
Bryce> works fine. The jikes-generated bytecode does, however, seem to
Bryce> work fine in the JDK VM.
It's possible that jikes is generating bad output and gcj is just more
strict than the JDK VM about what it accepts. I don't know. Can you
find out?
If it really is a gcj bug, we should change the test suite to let us
test compilation from .class files (that is, check in the generated
.class file).
Running the test suite against jikes would also be a nice thing to
do. Ideally someone would volunteer to do this periodically.
Tom