This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the GCJ project. See the GCJ home page for more information.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: first active use of a class

How does this interact with class loaders?  It would seem that class loaders
can load classes that the compiler could not have known about.
-----Original Message-----
From: Jerry Kramskoy <Jerry.Kramskoy@insignia.com>
To: Godmar Back <gback@cs.utah.edu>; java-discuss@sourceware.cygnus.com
<java-discuss@sourceware.cygnus.com>
Date: Thursday, April 08, 1999 6:30 AM
Subject: Re: first active use of a class


>
>>One issue was the issue of "first active use" of a class.
>>I pointed out that WAT compilers such as gcj are being penalized because
>>they have to insert code that checks for each possible first use of
>>a class whether its <clinit> initializer needs to be invoked.
>>
>>He said that his interpretation of the JLS gives such compiler writers
>>the freedom to preinitialize all classes before you even invoke the
>>main method; essentially saving that test.
>>
>
>I've had various conversations with one of Sun's JVM
...