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/5794: gcj fails to verify .class file generated by Sun JDK 1.4 compiler Date: Thu, 28 Feb 2002 22:56:00 -0000 [thread overview] Message-ID: <20020301002602.13970.qmail@sources.redhat.com> (raw) The following reply was made to PR java/5794; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: adam@medovina.org Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/5794: gcj fails to verify .class file generated by Sun JDK 1.4 compiler Date: 28 Feb 2002 17:47:43 -0700 >>>>> "Adam" == adam <adam@medovina.org> writes: Adam> Number: 5794 Adam> Synopsis: gcj fails to verify .class file generated by Sun JDK 1.4 compiler Could you upload the resulting .class file? Just reply to this email and attach it, keeping gcc-gnats on the CC line. Adam> When Sun's Java compiler in JDK 1.4 compiles a try...finally Adam> block, it emits a (useless and unused) exception table entry Adam> whose target is within the range of protected instructions. Adam> There is nothing inherently unsafe with this, but we check for Adam> this case and reject it in verify.c. It seems to me that this must be invalid. Adam> I tried that and then gcj complained about a stack overflow in Adam> the same .class file. Yeah. Suppose the VM encounters an internal error and throws an exception after it has set the PC to the start of the exception handler but before the first instruction of the handler (probably a pop or an astore) is executed. This leads inexorably to a stack overflow. I imagine the gij verifier will die on this too. I'd like to see the class file though. It's possible there are obscure extenuating circumstances. Or perhaps they've tightened the verification spec and I don't yet know about it. Tom
next reply other threads:[~2002-03-01 0:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-28 22:56 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-11 12:41 tromey 2002-03-02 17:16 Tom Tromey 2002-03-02 10:46 Adam Dingle 2002-03-02 10:36 Tom Tromey 2002-03-02 9:26 Adam Dingle 2002-03-01 0:06 Adam Dingle 2002-02-28 12:56 adam
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=20020301002602.13970.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).