陳韋任 <che...@iis.sinica.edu.tw> writes:
> Assume I want basic block register usage information, and
> I further assume that native machine has a register set
> {R0, R1, R2, R3}. The source code might be compiled into
> two basic blocks. What I want is something like,
>
> BB1 (0x100 - 0x120)
> In 0100
> Out 0010
>
> BB2 (0x121 - 0x130)
> In 1010
> Out 0001
>
> Here I use a bitmask with 1-bit for every physical register
> on the native machine. Every basic block has its live-ins/outs
> information with it. And I also want to assosicated each basic
> block with its corresponding binary (virtual) address.
But where do you want that information to be at runtime?
The hard part is not getting the information at compile time. The
information is readily available after register allocation. Heck, you
can see right in the dump files; e.g., use -da when you compile and look
at the pro_and_epilogue dump file.
The hard part is getting that information to be available at runtime.
Ian
