Displaying 5 results from an estimated 5 matches for "classllvm_1_1machinefunct".
2011 Jul 08
0
[LLVMdev] Best location in code generation for insertion of instrumentation to measure stack depth?
...nctions.
Assuming that it's possible, putting your functionality into a
MachineFunctionPass should be cleaner than modifying the code generator
directly (MachineFunctionPass'es may even be load-able into llc).
Check out the doxygen docs for MachineFunctionPass
(http://llvm.org/doxygen/classllvm_1_1MachineFunctionPass.html),
MachineFunction
(http://llvm.org/doxygen/classllvm_1_1MachineFunction.html), and
MachineFrameInfo
(http://llvm.org/doxygen/classllvm_1_1MachineFrameInfo.html).
-- John T.
>
> Thank you,
>
> Andrew
>
>
> _______________________________________________
> LL...
2011 Jul 08
2
[LLVMdev] Best location in code generation for insertion of instrumentation to measure stack depth?
...at it's possible, putting your functionality into a
> MachineFunctionPass should be cleaner than modifying the code generator
> directly (MachineFunctionPass'es may even be load-able into llc).
>
> Check out the doxygen docs for MachineFunctionPass (
> http://llvm.org/doxygen/classllvm_1_1MachineFunctionPass.html),
> MachineFunction (http://llvm.org/doxygen/classllvm_1_1MachineFunction.html),
> and MachineFrameInfo (
> http://llvm.org/doxygen/classllvm_1_1MachineFrameInfo.html).
>
> -- John T.
>
>
> Thank you,
>
> Andrew
>
>
> ____________________________...
2011 Jul 08
2
[LLVMdev] Best location in code generation for insertion of instrumentation to measure stack depth?
Hi list,
I am trying to implement the technique outlined in the following paper:
http://www.cs.umd.edu/~mwh/papers/martin10ownership.html in LLVM. My
approach so far involves the use of an IR level transform (via
runOnFunction) to identify memory loads and stores. One thing I need to do
(I am pretty sure I need to do it at least) is automatically mark each stack
frame as "owned" by the
2011 Jul 08
0
[LLVMdev] Best location in code generation for insertion of instrumentation to measure stack depth?
...tting your
> functionality into a MachineFunctionPass should be cleaner than
> modifying the code generator directly (MachineFunctionPass'es may
> even be load-able into llc).
>
> Check out the doxygen docs for MachineFunctionPass
> (http://llvm.org/doxygen/classllvm_1_1MachineFunctionPass.html),
> MachineFunction
> (http://llvm.org/doxygen/classllvm_1_1MachineFunction.html), and
> MachineFrameInfo
> (http://llvm.org/doxygen/classllvm_1_1MachineFrameInfo.html).
>
> -- John T.
>
>>
>> Thank you,
>>
>> Andr...
2013 Oct 09
4
[LLVMdev] Subregister liveness tracking
On Oct 8, 2013, at 2:06 PM, Akira Hatanaka <ahatanak at gmail.com> wrote:
> What I didn't mention in r192119 is that mthi/lo clobbers the other sub-register only if the contents of hi and lo are produced by mult or other arithmetic instructions (div, madd, etc.) It doesn't have this side-effect if it is produced by another mthi/lo. So I don't think making mthi/lo clobber the