[Jikesrvm-core] changes to bootimage writing

[David P G. <gr...@us...>]

I've just checked in a fairly hefty rewrite of the bootimage writer that 
has the effect of splitting the RVM bootimage into 2 files.  One file 
(RVM.code.image) contains all of the executable code in the bootimage, the 
other (RVM.data.image) contains all of the data.  The files are mapped to 
separate address ranges.  As far as the bootimage writer is concerned, the 
address ranges are completely arbitrary (but must not overlap).  Currently 
the VM/MMTk constrain things such that the bootimage data must be the 
lowest region of mapped memory, followed by the bootimage code, followed 
by the rest of the heap spaces.  It might be nice to generalize this to 
eliminate these constraints, but I think that's mainly a matter for MMTk, 
so I'll leave it to those who know it  better than I.

When you update from this change, if you maintain any local configuration 
files, instead of defining BOOTIMAGE_LOAD_ADDRESS, you must define both 
BOOTIMAGE_DATA_ADDRESS and BOOTIMAGE_CODE_ADDRESS.   I've updated all the 
config files in cvs (see rvm/config/* for examples if necessary) and on 
the nightly regression machines. 

I tested the changes on Linux/IA32, PowerPC/AIX/32 and PowerPC/AIX64. The 
nightly tests should pick up most of the other platforms, but if you see 
something broken let me know.

--dave