public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/19285] New: Interfaces not initialized by static field access
Date: Thu, 06 Jan 2005 02:19:00 -0000	[thread overview]
Message-ID: <20050106021930.19285.mckinlay@redhat.com> (raw)

Consider the following test case:

public class Test implements RuntimeConstants
{
  public static void main(String[] args)
  {
    System.out.println(foo[0]);
  }
}

interface RuntimeConstants 
{
  static int foo[] = {1};    
}

Older bytecode compilers would implement the access to "foo" like so:

  3: getstatic <Field RuntimeConstants.foo int[]>

However, presumably for reasons of binary compatibility, bytecode produced by
some modern Java compilers (javac 1.5.0 with "-target" >= 1.3) does the following:

  3: getstatic <Field Test.foo int[]>

When "foo" is actually in an interface, there is a problem for GCJ because we
have no way to ensure that the interface gets initialized when it is accessed.
Initialization of a class does not itself cause initialization of its
superinterfaces.

-- 
           Summary: Interfaces not initialized by static field access
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mckinlay 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=19285


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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06  2:19 mckinlay at redhat dot com [this message]
2005-01-06  2:19 ` [Bug java/19285] " mckinlay at redhat dot com
2005-01-06  2:56 ` tromey at gcc dot gnu dot org
2005-01-06 14:21 ` pinskia at gcc dot gnu dot org
2005-04-21 15:39 ` aph at gcc dot gnu dot org
2005-04-29 18:35 ` cvs-commit at gcc dot gnu dot org
2005-04-29 18:43 ` cvs-commit at gcc dot gnu dot org
2005-04-29 18:44 ` cvs-commit at gcc dot gnu dot org
2005-05-09 13:56 ` cvs-commit at gcc dot gnu dot org
2005-05-09 13:59 ` cvs-commit at gcc dot gnu dot org
2005-05-09 14:10 ` cvs-commit at gcc dot gnu dot org
2005-05-10 21:03 ` tromey at gcc dot gnu dot org

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=20050106021930.19285.mckinlay@redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).