[Bug java/12911] Class initialization optimization pessimization

[Bug java/12911] Class initialization optimization pessimization

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pinskia at gcc dot gnu dot
                   |                            |org
   Last reconfirmed|2004-08-24 01:13:36         |2004-11-06 19:07:09
               date|                            |


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

[Bug java/12911] Class initialization optimization pessimization

[pinskia at gcc dot gnu dot org]

-- 
Bug 12911 depends on bug 15576, which changed state.

Bug 15576 Summary: [4.0 Regression] Class initialization optimization is disabled
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15576

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

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

[Bug java/12911] Class initialization optimization pessimization

[aph at gcc dot gnu dot org]

------- Additional Comments From aph at gcc dot gnu dot org  2005-04-16 16:45 -------
*** Bug 21044 has been marked as a duplicate of this bug. ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aph at gcc dot gnu dot org


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

[Bug java/12911] Class initialization optimization pessimization

[aph at gcc dot gnu dot org]

------- 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