search for: smira

...LLVM, > but I've coded a spiller that prints the code in a format that the > debugger can read. The page is: > > http://compilers.cs.ucla.edu/fernando/projects/debugger/ Hi Fernando, This looks quite useful. Do you think you can incorporate the code output the debugging info in smira to tot? Also, it seems to make more sense to dump the info at the end of the register allocation pass. Is there any particular reason for you to add it to the spiller instead? Thanks, Evan > > all the best, > > Fernando > _______________________________________________ > L...

...o > refer to abstract frame indices. Wouldn't fernando's debugger use a > similar representation? I don't need it in the allocator. I need it in Fernando's spiller that prints the IR used by the debugger. The IR includes references to the stack pointer. I need to add some sMira IR instructions at the top of the function to define the stack pointer (and other things) so it isn't flagged as undefined by the debugger. I suppose we could change Fernando's IR so it works with abstract stack indices but there are other times I've wanted to know the stack pointer...

Hi guys, I have been using a debugger for my register allocator. The debugger happened to be very useful at catching register assignment errors. I've put the debugger on-line, if anyone who is working with register allocation wants to use. The debugger itself has nothing to do with LLVM, but I've coded a spiller that prints the code in a format that the debugger can read. The

Hi, Evan, > This looks quite useful. Do you think you can incorporate the code > output the debugging info in smira to tot? No problem. Actually, the spiller code is very small. If you have time, take a look: http://compilers.cs.ucla.edu/fernando/projects/debugger/src/PrintSpiller.txt To use it correctly, spill fusion must be disabled, otherwise the debugger will report the omitted load/stores as errors. F...

What's the "right" way to find out which machine register acts as the stack pointer? I'm working on enhancing Fernando's register allocator debugger and would like to add support for stack pointer semantics. TargetRegisterInfo has a getFrameRegister method but that returns (on x86) either ESP/RSP or EBP/RBP depending on whether frame pointer elimination has been done.

On Tue, 4 Mar 2008, David Greene wrote: > What's the "right" way to find out which machine register acts as the > stack pointer? I'm working on enhancing Fernando's register allocator > debugger and would like to add support for stack pointer semantics. > > TargetRegisterInfo has a getFrameRegister method but that returns > (on x86) either ESP/RSP or