Displaying 6 results from an estimated 6 matches for "classllvm_1_1machinefunctionpass".
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
>
>
> _______________________________________________
> LLVM Deve...
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,
>>
>> Andrew
>...
2011 Apr 05
0
[LLVMdev] instrument a byte code with llvm
...function. This external function will be implemented in a
run-time library that you link with the program after it is compiled
with LLVM.
The tricky part is to get the count of native code instructions. For
that, I think you'll need to write a MachineFunctionPass
(http://llvm.org/doxygen/classllvm_1_1MachineFunctionPass.html). This
sort of pass is part of the code generator and works on the IR
representing the generated code. You will need to have it count the
instructions and then modify the call instruction so that it passes the
count of machine instructions to the run-time library.
I haven't written...
2011 Apr 05
4
[LLVMdev] instrument a byte code with llvm
hi,
I'm newer in llvm
i would like to instrument a byte code with a pass and as a result i would
like to get an instrumented byte code.
i would like that a pass add a method (which calculate the number of
instructions) in the end of each block.
the instrumented code should contain in each block a method that calculate
the number of instructions
Please Help me
thank you
--
Nabila ABDESSAIED