This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
class initialization check overhead
- From: Adam Megacz <adam at megacz dot com>
- To: java at gcc dot gnu dot org
- Date: 23 Oct 2002 11:22:35 -0700
- Subject: class initialization check overhead
- Organization: Myself
I noticed that every static method has a check at the top of the
method to see if <clinit> needs to be run. Doesn't this incur
substantial overhead?
Could this be eliminated by putting each class (static data and code)
on its own page and write-protecting the page? Then you could catch
SIGSEGV and perform the initialization.
- a
--
"Through your rags I see your vanity" -- Socrates