public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/6163: anonymous class verifier error Date: Mon, 08 Apr 2002 10:36:00 -0000 [thread overview] Message-ID: <20020408173601.25279.qmail@sources.redhat.com> (raw) The following reply was made to PR java/6163; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: nferrier@tapsellferrier.co.uk Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/6163: anonymous class verifier error Date: 08 Apr 2002 11:35:54 -0600 >>>>> "Nic" == Nic Ferrier <nferrier@tapsellferrier.co.uk> writes: Nic> When compiling to byte-code source with anonymous classes GCJ Nic> produces code which causes verifier errors with Sun's Nic> interpreter. I looked at this. Are you using the 1.2 JDK? Sun changed the verifier a bit between 1.2 and 1.4. In particular they added a special exception for field initialization in <init> methods. This change is the root of the problem you are seeing. When I run the `gcj -C' output against the 1.2 java interpreter, I get a verification error. When I use the 1.4 interpreter, it works. It also works with gij (gij specifically implements this particular verifier change). Inspecting the <init> method in test$1.class, I see that the code in question is definitely one of these field assignments. So my current thinking is that this is not a bug. What do you think? Tom
next reply other threads:[~2002-04-08 17:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-08 10:36 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-06 15:46 tromey 2002-04-08 1:46 Nic Ferrier 2002-04-07 17:36 Tom Tromey 2002-04-03 16:36 nferrier
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=20020408173601.25279.qmail@sources.redhat.com \ --to=tromey@redhat.com \ --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: linkBe 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).