public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Adam Dingle <adam@medovina.org> 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: Sat, 02 Mar 2002 09:26:00 -0000 [thread overview] Message-ID: <20020302172601.14529.qmail@sources.redhat.com> (raw) The following reply was made to PR java/5794; it has been noted by GNATS. From: Adam Dingle <adam@medovina.org> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: java/5794: gcj fails to verify .class file generated by Sun JDK 1.4 compiler Date: Sat, 02 Mar 2002 09:20:27 -0800 --Boundary_(ID_SqrWNdAHJp+UIEkskG5ToA) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Another note. I tried compiling the same source file with Sun's JDK 1.3 compiler. It compiled the method differently, and did not generate any exception table entry with a target address inside the range of addresses which the entry itself protects. Nevertheless, GCJ 3.0.2 still fails to verify the class; it reports Foo.java: In class `Foo': Foo.java: In method `Foo.invoke()': Foo.java:6: verification error at PC=11 Foo.java:6: stack overflow The method's disassembly looks like this: Method int invoke() 0 iconst_1 1 istore_1 2 jsr 13 5 iload_1 6 ireturn 7 astore_2 8 jsr 13 11 aload_2 12 athrow 13 astore_3 14 iconst_3 15 ireturn Exception table: from to target type 0 7 7 any I've included the .class file generated by the JDK 1.3 compiler as an attachment to this message. (I found another test case where the compiler generates code which causes GCJ to seg fault, but I'll file a separate bug report for that one.) adam ------------------------------------------------------- --Boundary_(ID_SqrWNdAHJp+UIEkskG5ToA) Content-type: application/java; charset=iso-8859-1; name=Foo.class Content-transfer-encoding: base64 Content-disposition: attachment; filename=Foo.class yv66vgADAC0ADwoAAwAMBwANBwAOAQAGPGluaXQ+AQADKClWAQAEQ29kZQEAD0xpbmVOdW1iZXJU YWJsZQEABmludm9rZQEAAygpSQEAClNvdXJjZUZpbGUBAAhGb28uamF2YQwABAAFAQADRm9vAQAQ amF2YS9sYW5nL09iamVjdAAhAAIAAwAAAAAAAgABAAQABQABAAYAAAAdAAEAAQAAAAUqtwABsQAA AAEABwAAAAYAAQAAAAEAAQAIAAkAAQAGAAAANAABAAQAAAAQBDyoAAsbrE2oAAUsv04FrAABAAAA BwAHAAAAAQAHAAAACgACAAAABgAHAAgAAQAKAAAAAgAL --Boundary_(ID_SqrWNdAHJp+UIEkskG5ToA)--
next reply other threads:[~2002-03-02 17:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-02 9:26 Adam Dingle [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-01 0:06 Adam Dingle 2002-02-28 22:56 Tom Tromey 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=20020302172601.14529.qmail@sources.redhat.com \ --to=adam@medovina.org \ --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).