Displaying 8 results from an estimated 8 matches for "addpassestoemit".
Did you mean:
addpassestoemitmc
2007 Jan 22
0
[LLVMdev] addPassesToEmit(Whole)File changes?
Hi folks,
just installed the new llvm 1.9 build and noticed that my code no
longer worked. It seems something has changed with
addPassesToEmitFile(). First, the arguments to that method changed so
that it no longer takes a PassManager, but only a
FunctionPassManager. Instead there is a addPassesToEmitWholeFile()
method, but that is marked as optional, and when I change my code to
use that there is no output (only an empty file)....
2007 Jan 22
0
[LLVMdev] addPassesToEmit(Whole)File changes?
On Sun, 21 Jan 2007, Marcel Weiher wrote:
> just installed the new llvm 1.9 build and noticed that my code no
> longer worked. It seems something has changed with
> addPassesToEmitFile(). First, the arguments to that method changed so
> that it no longer takes a PassManager, but only a
> FunctionPassManager. Instead there is a addPassesToEmitWholeFile()
> method, but that is marked as optional, and when I change my code to
> use that there is no output (only an...
2007 Jan 22
2
[LLVMdev] addPassesToEmit(Whole)File changes?
Hi folks,
just installed the new llvm 1.9 build and noticed that my code no
longer worked. It seems something has changed with
addPassesToEmitFile(). First, the arguments to that method changed so
that it no longer takes a PassManager, but only a
FunctionPassManager. Instead there is a addPassesToEmitWholeFile()
method, but that is marked as optional, and when I change my code to
use that there is no output (only an empty file)....
2009 Jul 14
0
[LLVMdev] Writing pass for llc
...lc.cpp?
>
> I would like to be able to write a pass that looks at MachineFunctions
> and inserts instructions right before register allocation (but after
> all other optimization/instruction selection passes). Any direction/
> advice would be of great help. Thanks!
llc uses Target.addPassesToEmit* interface to add passes. You can
insert your pass at appropriate place here.
-
Devang
2009 Jul 12
3
[LLVMdev] Writing pass for llc
Is there a beginner's tutorial/documentation on how to write passes
for the llc tool? I've managed to write some simple analysis passes
for the opt tool but can't figure out how to do the same for llc.
What is the proper way to integrate a new MachineFunction pass with
llc? Is there a way to register passes and selectively enable them on
the command line (as with opt) or do I need to
2007 Jul 09
2
[LLVMdev] Pluggable Register Coalescers
...started the refactoring work.
I'm in the midst of finishing up an implementation following the model of how
register allocators are selected. Thgere may be some more refactoring/code
sharing work to be done with this, but I want to get it working first.
createRegisterAllocator() is called by addPassesToEmit.* to instantiate the
register allocator.
Coalescing is a bit different. Typically, the register allocator is the
client of the coalescer. My original thought was to have each register
allocator implementation call createRegisterCoalescer directly. I then
thought it might be better to have allo...
2009 Jul 15
2
[LLVMdev] Writing pass for llc
...e able to write a pass that looks at MachineFunctions
>> and inserts instructions right before register allocation (but after
>> all other optimization/instruction selection passes). Any direction/
>> advice would be of great help. Thanks!
>>
>
> llc uses Target.addPassesToEmit* interface to add passes. You can
> insert your pass at appropriate place here.
>
> -
> Devang
>
>
One related question.
Can we write CallGraphSCCPass in llc?
- Sanjiv
2007 Jul 09
0
[LLVMdev] Pluggable Register Coalescers
...>
> I'm in the midst of finishing up an implementation following the model of how
> register allocators are selected. Thgere may be some more refactoring/code
> sharing work to be done with this, but I want to get it working first.
>
> createRegisterAllocator() is called by addPassesToEmit.* to instantiate the
> register allocator.
>
> Coalescing is a bit different. Typically, the register allocator is the
> client of the coalescer. My original thought was to have each register
> allocator implementation call createRegisterCoalescer directly. I then
> thought i...