java/5227: verification error on JDK 1.3.1 class file

[Daniel Bonniot]

Hi,

I have tried reproducing the following bug, which was reported against 
gcc version 3.1 20011230 (experimental):

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5227

The bug seems to have been fixed, in gcc version 3.3 20030412 (Debian 
prerelease):
$ gcj-3.3 -I/usr/share/java/libgcj-3.3.jar 
-I/usr/lib/j2se/1.3/jre/lib/rt.jar  -c ReaderThread.class
IIOPConnection.java: In class `com.sun.corba.se.internal.iiop.ReaderThread':
IIOPConnection.java: In method 
`com.sun.corba.se.internal.iiop.ReaderThread.run()':
IIOPConnection.java:139: warning: unreachable bytecode from 171 to 
before 174
IIOPConnection.java:141: warning: unreachable bytecode from 178 to 
before 180

So there are two warnings, but no verification error anymore.

Just to make sure, I tried to reproduce the bug with an older version of 
gcj, to check my setup is correct. With gcc version 3.0.4, I do 
reproduce the bug:

$ gcj-3.0 -I/usr/share/java/libgcj-3.3.jar 
-I/usr/lib/j2se/1.3/jre/lib/rt.jar  -c ReaderThread.class
IIOPConnection.java: In class `com.sun.corba.se.internal.iiop.ReaderThread':
IIOPConnection.java: In method 
`com.sun.corba.se.internal.iiop.ReaderThread.run()':
IIOPConnection.java:100: verification error at PC=178
IIOPConnection.java:100: stack overflow


So I suggest to close this bug as fixed. Cheers!

Daniel

PS: gcj 3.3 does generate lots of spurious warnings about unreachable 
bytecode, like in the above output. Is this a known problem. Should a 
bug report be filed about them?