public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Daniel Bonniot <Daniel.Bonniot@inria.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/5537: Error compiling simple bytecode with jsr Date: Thu, 31 Jan 2002 02:06:00 -0000 [thread overview] Message-ID: <20020131100600.4941.qmail@sources.redhat.com> (raw) The following reply was made to PR java/5537; it has been noted by GNATS. From: Daniel Bonniot <Daniel.Bonniot@inria.fr> To: tromey@redhat.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/5537: Error compiling simple bytecode with jsr Date: Thu, 31 Jan 2002 10:56:09 +0100 Tom Tromey wrote: > > I've looked at this. gcj still rejects the bytecode in this PR. I > think it does so incorrectly; the bytecode looks fine to me and both > `java' and `gij' pass it. > > How did you generate the bytecode? The bytecode is the output of Sun/Blackdown javac 1.3.1 on the given A.java The error was first found with my own compiler (http://nice.sf.net) that generates java bytecode and now optionally calls gcj on the ouput. > If you did so with gcj, note that > gcj 3.1 no longer generates the same bytecode. Now the method is > simply `return'. I suppose this is only an optim due to the fact that the finally block is empty. I tried to find the smallest case that triggers the problem. I have gcj 3.0.3 and it works fine on the source. I haven't tried to make it produce bytecode. > This doesn't affect the fact that this is a gcj bug. Right.
next reply other threads:[~2002-01-31 10:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-31 2:06 Daniel Bonniot [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-12 19:21 Dara Hazeghi 2002-10-08 1:06 Daniel Bonniot 2002-01-30 15:36 Tom Tromey 2002-01-30 4:26 Daniel.Bonniot
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=20020131100600.4941.qmail@sources.redhat.com \ --to=daniel.bonniot@inria.fr \ --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).