Frederick Ryckbosch <frederick.ryckbosch@...> wrote on 06/16/2009 09:10:24 AM:
>
> Perhaps my question is not clear enough.
>
> What I basically need is a map between bytecodes and assembler for the
> opt compiler.
> I've seen articles where people added this to JikesRVM.
We do this for a subset of the machine instructions already in the opt compiler. If an IR instruction is tagged as being a GC point or a PEI, then an entry is generated in the opt compiler's machinecode maps that allows the runtime system to map from the machinecode instruction back to the source level bytecode. In theory, you could use this same mapping mechanism to get the maps you want by ensuring that the IR instructions that were generated from the bytecode of interest were tagged as needing machine code map entries. Take a look at OptCompiledMethod and OptMachineCodeMap.
We don't do it for all instructions because of (a) space overheads for the mapping info and (b) as the optimizer does various transformations it's not always totally clear what bytecode instruction should be associated with a given IR/machinecode instruction.
--dave
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Jikesrvm-researchers mailing list
Jikesrvm-researchers@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers
