[PATCH] D20769: [IPRA] Interprocedural Register Allocation - Analysis Passes

[Vivek Pandya via llvm-commits]

vivekvpandya added inline comments.

================
Comment at: test/CodeGen/Generic/reg-usage-info.ll:4
@@ +3,3 @@
+; CHECK: Function Name : fib
+; CHECK: Clobbered Registers: 1 3 19 35 2 3 19 35 4 8 21 37 5 8 21 37 15 14 23 39 25 1 3 19 35 2 3 19 35 7 6 20 36 4 8 21 37 5 8 21 37 48 47 30 44
+
----------------
vivekvpandya wrote:
> mehdi_amini wrote:
> > I'm worried that we don't provide any stability guarantee on the numbers printed here.
> > Having a nicer textual form would be better. 
> > I just don't see how to do it other than keep a pointer to the TRI in the DenseMap in the immutable pass to be able to get the register name.
> If RegUsageInfoCollector is considered as analysis pass then we can add cl::opt into that file and have analysis printed from that.
Will TRI pointer assigned a value by the MachineFunction pass ? Or Is there any way to get TargetMachine or TargetRegisterInfo from Module object? Also if PReg name is required to be printed then MCRegisterInfo will be required.


http://reviews.llvm.org/D20769