Re: Patch: Remove JvAllocObject and add fields to Class for interpreter/JIT data

[Andrew Haley <aph at redhat dot com>]

Tom Tromey writes:
 > >>>>> "Bryce" == Bryce McKinlay <mckinlay@redhat.com> writes:
 > 
 > Bryce> Please comment on the following patch, particularly the names and
 > Bryce> nature of the new fields in Class.h
 > 
 > I think this general idea is great and long overdue.
 > 
 > Bryce> 	* java/lang/Class.h (Class): Add new fields `aux_id' and 
 > Bryce> 	`aux_info'.
 > 
 > aux_id isn't used (except in the GC) or set.  What if we just remove
 > it for the time being?  I think we'll need something like this, but I
 > think we should hold off on it until we do some actual design on the
 > pluggable execution engine idea.
 > 
 > Also, on irc we talked about moving `otable' and `atable' and friends
 > out of the Class structure and into `aux_info'.  Do we still want to
 > do that?  I suppose this could wait to some later stage as well.

We need to be sure that we can access atable/otable entries via a
single memory load insn, so they have to be in the compiler-allocated
static memory space.

Andrew.