heap fragmentation?

Mon Jun 10 20:34:00 GMT 2002

>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:

Jeff> If all static members can be addressed at constant offsets from
Jeff> the class pointer, that takes care of the class initialization
Jeff> test we do now.
Could you explain this to me? It seems to me that we'll still need a
test, because the class will be dynamically created. So at an active
use site we'll have to see if it has been created, presumably by
making a synchronized method call. Hopefully I'm missing something.
Hmm, right now we seem to do "double checked locking" when checking
the class initialization status. At least that's what it looks like:
	cmpb	12,ドル _ZN4java4lang6System6class$E+74
	setge	%al
	movb	%al, -1(%ebp)
	cmpb	0,ドル -1(%ebp)
	jne	.L3
	movl	$_ZN4java4lang6System6class$E, (%esp)
	call	_Jv_InitClass
Isn't that a no-no?
Jeff> (gcj -C isn't quite ready for executable bytecode)
I know of a few `gcj -C' code generation bugs. They are all in Gnats.
Are these the ones you're referring to? Or are there more I don't
know about?
Note that the .class front end isn't perfect either. There is at
least one bug without a workaround in Gnats.
Tom