Displaying 5 results from an estimated 5 matches for "mpmanager".
Did you mean:
opmanager
2008 Jan 29
4
[LLVMdev] PassManager Mysteries
On Monday 28 January 2008 09:31:11 pm Owen Anderson wrote:
> From experience, an important point that is often forgotten is that
> the order of declaration of dependencies matter. If you declare that
> you require pass A, and then pass B, and B doesn't preserve A, you'll
> get an error like this.
>
> Just some advice from having had similar problems in the past.
2018 May 07
2
Preservation of CallGraph (by BasicBlockPass, FunctionPass)
...set CallGraphUpToDate=false;) in case modification had been done. Thus, it seems to be legit for a FunctionPass (and thereby also the FunctionPassManager) to not always preserve the CallGraph. And I think this is handled within the CGPassManager, but not when FPManager is executed directly from the MPManager
Currently the test case above will end up in an assert, since there is a missing use of @f1 in the CallGraph when doing the inlining.
That will go away if I remove the setPreservesAll from the FPPassManager:: getAnalysisUsage (which I assume is too aggressive).
Would it be correct to change the F...
2018 May 07
0
Preservation of CallGraph (by BasicBlockPass, FunctionPass)
...e=false;) in case modification had been done. Thus, it seems
> to be legit for a FunctionPass (and thereby also the FunctionPassManager) to
> not always preserve the CallGraph. And I think this is handled within the
> CGPassManager, but not when FPManager is executed directly from the
> MPManager
>
>
>
> Currently the test case above will end up in an assert, since there is a
> missing use of @f1 in the CallGraph when doing the inlining.
>
> That will go away if I remove the setPreservesAll from the FPPassManager::
> getAnalysisUsage (which I assume is too aggressive...
2018 May 08
2
Preservation of CallGraph (by BasicBlockPass, FunctionPass)
...had been done. Thus, it
> seems
> > to be legit for a FunctionPass (and thereby also the FunctionPassManager)
> to
> > not always preserve the CallGraph. And I think this is handled within the
> > CGPassManager, but not when FPManager is executed directly from the
> > MPManager
> >
> >
> >
> > Currently the test case above will end up in an assert, since there is a
> > missing use of @f1 in the CallGraph when doing the inlining.
> >
> > That will go away if I remove the setPreservesAll from the FPPassManager::
> > getAnalysi...
2018 May 08
0
Preservation of CallGraph (by BasicBlockPass, FunctionPass)
...> > > to be legit for a FunctionPass (and thereby also the
> FunctionPassManager)
> > to
> > > not always preserve the CallGraph. And I think this is handled within
> the
> > > CGPassManager, but not when FPManager is executed directly from the
> > > MPManager
> > >
> > >
> > >
> > > Currently the test case above will end up in an assert, since there is
> a
> > > missing use of @f1 in the CallGraph when doing the inlining.
> > >
> > > That will go away if I remove the setPreservesAll from...