This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: class initialization check overhead
- From: Tom Tromey <tromey at redhat dot com>
- To: Anthony Green <green at redhat dot com>
- Cc: "C. van Reeuwijk" <C dot vanReeuwijk at its dot tudelft dot nl>, java at gcc dot gnu dot org
- Date: 25 Nov 2002 22:57:02 -0700
- Subject: Re: class initialization check overhead
- References: <Pine.LNX.4.44.0210232230290.10620-100000@ops2.one-point.com><867kg81ml3.fsf@nowhere.com> <3DB7ACB9.5030603@trifork.com><20021024091024.GA4020@falcon.pds.twi.tudelft.nl><1035462885.1782.34.camel@dhcppc2>
- Reply-to: tromey at redhat dot com
>>>>> "Anthony" == Anthony Green <green@redhat.com> writes:
>> On Thu, 2002-10-24 at 02:10, C. van Reeuwijk wrote:
>> - Within a method, keep track of the classes already initialized,
>> and don't initialize a class again if you know for sure that it, or a
>> subclass, has already been initialized.
Anthony> I know we used to do this (without the subclass trick), by generating
Anthony> something like the following for "x = foo.bar.y"...
I like the subclass trick, and I submitted a PR for this.
We still do the class initialization optimization you mention. I
don't remember it changing greatly since it was first implemented
(though maybe I missed something).
Tom