public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "aph at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/12911] Class initialization optimization pessimization
Date: Tue, 03 May 2005 13:34:00 -0000	[thread overview]
Message-ID: <20050503133446.21453.qmail@sourceware.org> (raw)
In-Reply-To: <20031105143639.12911.green@redhat.com>


------- Additional Comments From aph at gcc dot gnu dot org  2005-05-03 13:34 -------
I'm tempted to change this to WONTFIX.

The patch for PR java/19285 party fixes this for indirect dispatch: in A.foo2(),
 the field B.bar is initialized by a call to _Jv_ResolvePoolEntry, and this is
only called once, the first time A.foo2() is invoked.

Granted, this only applies to the indirect dispatch (a.k.a. the "new ABI") case.
 However, optimizing known incorrect behaviour doesn't seem like a good use of
anyone's time.

Because of the binary compatibility rules we can't assume that B.bar will always
be a field of B; it might be a field of one of B's interfaces.  Initializing B
won't initialize its interfaces, so this code will fail.



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |SUSPENDED


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


      parent reply	other threads:[~2005-05-03 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031105143639.12911.green@redhat.com>
2004-11-06 19:07 ` pinskia at gcc dot gnu dot org
2004-11-09 14:37 ` pinskia at gcc dot gnu dot org
2005-04-16 16:45 ` aph at gcc dot gnu dot org
2005-05-03 13:34 ` aph at gcc dot gnu dot org [this message]

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=20050503133446.21453.qmail@sourceware.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).