public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/17488] New: Binary compatibility: must ensure static method's class remains live
Date: Tue, 14 Sep 2004 22:13:00 -0000	[thread overview]
Message-ID: <20040914221256.17488.tromey@gcc.gnu.org> (raw)

At the moment, a reference to a static method won't cause the
method's class to be considered as live.  This can lead to
incorrect collection of the class.  The fix is to somehow
arrange for this class to be marked.

For static fields this is handled because we emit explicit
_Jv_InitClass calls for the field's class; the class reference
ends up in the constant pool and is marked there.

One potential fix would be to move class initialization calls
for static methods to the caller (they are now in the callee).
This might be difficult (there are many calls from C++, for instance).

-- 
           Summary: Binary compatibility: must ensure static method's class
                    remains live
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tromey at gcc dot gnu dot org
                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=17488


             reply	other threads:[~2004-09-14 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 22:13 tromey at gcc dot gnu dot org [this message]
2004-09-14 22:13 ` [Bug java/17488] " pinskia at gcc dot gnu dot org
2004-09-14 22:13 ` 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=20040914221256.17488.tromey@gcc.gnu.org \
    --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).