Displaying 3 results from an estimated 3 matches for "addassemblyemitter".
2010 Jul 28
3
[LLVMdev] Function-at-a-time Processing
...n pass
manager gets deleted, it destroys the MCContext alonmg with it.
Actually, the AsmPrinter destroys the MCContext through a reference (!)
which makes things all the more confusing. When the module pass manager
comes along and tries of access an MCSection, everything blows up.
I had to re-add addAssemblyEmitter to LLVMTargetMachine to try to make
this work. It essentially takes the AsmPrinter creation bits from
addPassesToEmitFile and packages them into a separate function.
[As a side note, I don't understand how the two AsmPrinters (one for the
module pass manager, one for the function pass manager...
2010 Jul 28
0
[LLVMdev] Function-at-a-time Processing
...ted, it destroys the MCContext alonmg with it.
> Actually, the AsmPrinter destroys the MCContext through a reference (!)
> which makes things all the more confusing. When the module pass manager
> comes along and tries of access an MCSection, everything blows up.
>
> I had to re-add addAssemblyEmitter to LLVMTargetMachine to try to make
> this work. It essentially takes the AsmPrinter creation bits from
> addPassesToEmitFile and packages them into a separate function.
>
> [As a side note, I don't understand how the two AsmPrinters (one for the
> module pass manager, one for t...
2007 Nov 09
1
[LLVMdev] Newbie JITter
Thanks Evan.
On 09/11/2007, at 6:50 PM, Evan Cheng wrote:
>> 1. What optimization passes, if any, should I run on the module
>> before I pass it to the ExecutionEngine.
>
> The default JIt driver, lli, runs everything.
My reading of the lli source indicates that it's not explicitly doing
any opt passes - is that happening implicitly in the ExecutionEngine?
I can see