public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "overholt at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/19295] New: Incorrect bytecode produced for bitwise AND
Date: Thu, 06 Jan 2005 19:14:00 -0000	[thread overview]
Message-ID: <20050106191430.19295.overholt@redhat.com> (raw)

This is a boiled-down test case from part of Eclipse.  gcj produces this bytecode:

Method name:"isArrayType" public final Signature: ()boolean
Attribute "Code", length:35, max_stack:3, max_locals:1, code_length:11
  0: aload_0
  1: getfield <Field Test2.tagBits long>
  4: i2l

which results in a verification failure because it's producing an i2l
instruction when there's a long on the stack.

gcj4 --version
gcj4 (GCC) 4.0.0 20041228 (Red Hat 4.0.0-0.17) (i686-pc-linux)

$ gcj4 -C Test2.java; gcj4 -findirect-dispatch -c Test2.class
Test2.java: In class 'Test2':
Test2.java: In method 'Test2.isArrayType()':
Test2.java:5: error: verification failed: incompatible type on stack
Test2.java:5: error: expected type 'int' but stack contains 'void'
Test2.java:5: confused by earlier errors, bailing out

-- 
           Summary: Incorrect bytecode produced for bitwise AND
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: overholt at redhat dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19295


             reply	other threads:[~2005-01-06 19:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 19:14 overholt at redhat dot com [this message]
2005-01-06 19:15 ` [Bug java/19295] " overholt at redhat dot com
2005-01-06 20:00 ` [Bug java/19295] [4.0 regression] " tromey at gcc dot gnu dot org
2005-01-06 20:04 ` pinskia at gcc dot gnu dot org
2005-01-19 18:52 ` mmitchel at gcc dot gnu dot org
2005-01-19 19:24 ` steven at gcc dot gnu dot org
2005-01-19 22:37 ` tromey at gcc dot gnu dot org
2005-01-19 22:44 ` mark at codesourcery dot com
2005-01-24 14:34 ` cvs-commit at gcc dot gnu dot org
2005-01-24 14:41 ` pinskia at gcc dot gnu dot org
2005-02-11  8:36 ` overholt at redhat dot com

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=20050106191430.19295.overholt@redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).