Displaying 5 results from an estimated 5 matches for "removedeadpasses".
2013 Nov 19
2
[LLVMdev] Some MCJIT benchmark numbers
...ime is spent in PassManagerImpl::run, and another 47% is spent
in addPassesToEmitMC, which feels like it could be avoided by doing that
just once. Of the time spent in PassManagerImpl::run, about 35% is spent
in PassManager overhead such as initializeAnalysisImpl() /
removeNotPreservedAnalysis() / removeDeadPasses().
For 10k iterations, the test took about 12.6s, or 1.26ms per module, so
there's definitely some slowdown happening. Looking at the profiling
output, it looks like the main difference is the appearance of
MCJIT::finalizeLoadedModules(), which ultimately calls
RuntimeDyldImpl::resolveRelocat...
2013 Nov 19
0
[LLVMdev] Some MCJIT benchmark numbers
...ManagerImpl::run, and another 47% is spent
> in addPassesToEmitMC, which feels like it could be avoided by doing that
> just once. Of the time spent in PassManagerImpl::run, about 35% is spent
> in PassManager overhead such as initializeAnalysisImpl() /
> removeNotPreservedAnalysis() / removeDeadPasses().
>
> For 10k iterations, the test took about 12.6s, or 1.26ms per module, so
> there's definitely some slowdown happening. Looking at the profiling
> output, it looks like the main difference is the appearance of
> MCJIT::finalizeLoadedModules(), which ultimately calls
> Ru...
2016 May 25
0
PassManager insights?
...ver, it does not. I wonder if this is an error, but when I insert removal in that function, other stuff breaks, so I'm led to believe that the removeNotPreservedAnalysis() isn't meant to go that deep, and instead just clean up some map. Perhaps the CallGraph should be removed a bit later in removeDeadPasses() instead? But it is not in the relevant lastuse-map. Perhaps that's the bug? Or something else entirely.
If find the PassManagers a bit hard to get a good grip of, so any help and insights would be greatly appreciated!
BR, Jesper
-------------- next part --------------
An HTML attachment was...
2012 Apr 22
0
[LLVMdev] Remove function from module
Михаил wrote:
> It is ModulePass with AnalysisUsage of CallGraph
Ah, then you'll need to update the CallGraph first. Use
"CG.removeFunctionFromModule(F);" before deleting it.
Nick
> Yours sincerely,
> Kadysev Mikhail
>
> 22.04.2012, в 5:20, Nick Lewycky написал(а):
>
>> Михаил wrote:
>>> Thanks, but I replaceAllUsesWith() - works well, but I still
2012 Apr 22
2
[LLVMdev] Remove function from module
It is ModulePass with AnalysisUsage of CallGraph
Yours sincerely,
Kadysev Mikhail
22.04.2012, в 5:20, Nick Lewycky написал(а):
> Михаил wrote:
>> Thanks, but I replaceAllUsesWith() - works well, but I still get bug in
>> eraseFromParent():
>>
>> While deleting: i32 (%class.B*, i32)* %_ZN1B1xEi
>> An asserting value handle still pointed to this value!
>>