Displaying 2 results from an estimated 2 matches for "a04e6fc765eeb0c4c90ac5d55113db116".
2017 Jun 05
2
Question about llvm::Value::print performance
Hi,
I want to use llvm::Value::print to output the assembly strings for llvm::Instructions
inside a rather large llvm::Module (linked module with lots of types/...).
I started with plain ::print and switched over to
http://llvm.org/docs/doxygen/html/classllvm_1_1Value.html#a04e6fc765eeb0c4c90ac5d55113db116
with a ModuleSlotTracker I pass in myself to avoid some complexity.
Still now I have the issue that the TypeFinder::run and related that is done internally
by each print still is 99% of my program runtime. (at least perf tells me that)
Is there any clever workaround for this?
I looked a bit thr...
2017 Jun 05
2
Question about llvm::Value::print performance
...output the assembly strings for
>> llvm::Instructions
>> inside a rather large llvm::Module (linked module with lots of
>> types/...).
>>
>> I started with plain ::print and switched over to
>>
>> http://llvm.org/docs/doxygen/html/classllvm_1_1Value.html#a04e6fc765eeb0c4c90ac5d55113db116
>>
>> with a ModuleSlotTracker I pass in myself to avoid some complexity.
>>
>> Still now I have the issue that the TypeFinder::run and related that
>> is done internally
>> by each print still is 99% of my program runtime. (at least perf tells
>> me that...