public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/7066: gcj generates invalid bytecode for inner classes Date: Tue, 18 Jun 2002 09:56:00 -0000 [thread overview] Message-ID: <20020618163605.24541.qmail@sources.redhat.com> (raw) The following reply was made to PR java/7066; it has been noted by GNATS. From: Bruno Haible <bruno@clisp.org> To: tromey@redhat.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/7066: gcj generates invalid bytecode for inner classes Date: Tue, 18 Jun 2002 18:23:56 +0200 (CEST) Tom Tromey writes: > This means you didn't configure with --enable-threads, but your > program uses threads. I see. Thanks. > Bruno> $ java -version > Bruno> java version "1.3.1_02" > > This is part of the problem... > > Bruno> Method GetURL$1(GetURL) > Bruno> 0 aload_0 > Bruno> 1 aload_1 > Bruno> 2 putfield #12 <Field GetURL this$0> > Bruno> 5 aload_0 > Bruno> 6 invokespecial #15 <Method java.lang.Thread()> > Bruno> 9 return > > This is valid bytecode according to the 1.4 spec. The 1.3 JDK doesn't > like it though; they added a special exception to the verifier to let > code like this through. If you use the 1.4 "javac" you'll also see > this. Thanks for the explanation. Is there a command line option for gcj to produce Java 1.1 compliant class files? I mean, without such an option, "gcj -C" is useless for me. I wanted to bytecompile Java sources to jars and distribute them as jar files, to be executed by any JDK 1.1 compliant JVM. Bruno
next reply other threads:[~2002-06-18 16:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-18 9:56 Bruno Haible [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-18 14:36 Tom Tromey 2002-06-18 8:07 Tom Tromey 2002-06-18 8:07 Bruno Haible
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=20020618163605.24541.qmail@sources.redhat.com \ --to=bruno@clisp.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).