Displaying 3 results from an estimated 3 matches for "memoryssawrapperpass".
2020 Oct 02
2
Pass dependency error
...uto* kernel : kernels)
getAnalysis<SimplifyGEPPass>().runOnFunction(*kernel);
DetectKernelsPass works fine but i am getting the error for
SimplifyGEPPass and i can't figure out why. Are FunctionPasses not
supposed to be used inside ModulePasses like that?
I also tried some llvm pass (MemorySSAWrapperPass) but i'm getting the
same error:
AnalysisType &llvm::Pass::getAnalysisID(llvm::AnalysisID) const
[AnalysisType = llvm::MemorySSAWrapperPass]: Assertion `ResultPass &&
"getAnalysis*() called on an analysis that was not " "'required' by
pass!"' f...
2018 Aug 11
3
ScalarEvolution in a ModulePass
...and see if you might have more insights into this problem. For
example, I'm not totally sure why the other analysis FunctionPasses cause
ScalarEvolutionWrapperPass::runOnFunction() to rerun. I'm also concerned
about other analysis FunctionPasses, that might suffer from the same
problem. MemorySSAWrapperPass, for example, uses a unique_ptr similarly to
ScalarEvolution.
Cheers,
TB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180811/8d58a7bb/attachment.html>
2016 Oct 31
1
[PATCH] D26127: [MemorySSA] Repair AccessList invariants after insertion of new MemoryUseOrDef.
...ticular order.
It should be possible to do it all in a single iteration, either bottom up
or top down.
Many of the transforms in this pass
> create entirely new memsets, memcpys, and memmoves (among others). After
> each
> new insertion, I expect to also have to update MSSA since 1)
> MemorySSAWrapperPass is delcared preserved to the pass manager, and 2)
> subsequent MCO iterations which depend on MSSA need to be able to see,
> analyze,
> and possibly further transform these newly added meminsts.
>
Can you give an example of a case where, processing in top-down order,
going from defs to...