public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Bonniot <Daniel.Bonniot@inria.fr>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5227: verification error on JDK 1.3.1 class file
Date: Mon, 21 Apr 2003 21:26:00 -0000	[thread overview]
Message-ID: <20030421212601.25676.qmail@sources.redhat.com> (raw)

The following reply was made to PR java/5227; it has been noted by GNATS.

From: Daniel Bonniot <Daniel.Bonniot@inria.fr>
To: gcc-gnats@gcc.gnu.org,  Jens.Maurer@gmx.net,  java-prs@gcc.gnu.org, 
 gcc-bugs@gcc.gnu.org,  nobody@gcc.gnu.org,  gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: java/5227: verification error on JDK 1.3.1 class file
Date: Mon, 21 Apr 2003 23:21:18 +0200

 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?
 


             reply	other threads:[~2003-04-21 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-21 21:26 Daniel Bonniot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  6:24 steven
2001-12-31  4:26 Jens.Maurer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030421212601.25676.qmail@sources.redhat.com \
    --to=daniel.bonniot@inria.fr \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).