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/5812: GCJ 3.0.2 segfaults on class file from Sun JDK 1.3 compiler Date: Sat, 02 Mar 2002 12:16:00 -0000 [thread overview] Message-ID: <20020302201601.12679.qmail@sources.redhat.com> (raw) The following reply was made to PR java/5812; it has been noted by GNATS. From: Adam Dingle <adam@medovina.org> To: tromey@redhat.com Cc: gcc-gnats@gcc.gnu.org, Per Bothner <per@bothner.com> Subject: Re: java/5812: GCJ 3.0.2 segfaults on class file from Sun JDK 1.3 compiler Date: Sat, 02 Mar 2002 12:05:35 -0800 > However, given that Sun's compiler generated this, perhaps they intend > that we only verify reachable code. In this case, the `return' is not > reachable since there is no `ret' corresponding to the `jsr'. I'm pretty sure that Sun verifies only reachable code and believes that this is what a byte code verifier should do. The description of the bytecode verification process in section 4.9.2 of the Java Virtual Machine Specification describes a data-flow analyzer which will ignore unreachable code; see http://java.sun.com/docs/books/vmspec/2nd-edition/html/ClassFile.doc.html#9801 -adam
next reply other threads:[~2002-03-02 20:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-02 12:16 Adam Dingle [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-25 22:27 tromey 2002-03-05 11:36 Per Bothner 2002-03-02 11:06 Per Bothner 2002-03-02 10:46 Tom Tromey 2002-03-02 10:16 Alexandre Petit-Bianco 2002-03-02 8: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=20020302201601.12679.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).