Displaying 7 results from an estimated 7 matches for "bbpassmanag".
Did you mean:
bbpassmanager
2018 May 07
2
Preservation of CallGraph (by BasicBlockPass, FunctionPass)
...getAnalysisUsage to exclude "CallGraph Construction" from the set of preserved analyses, or am I missing something here?
I assume that DeadInstElimination isn't preserving the CallGraph. Shouldn't that (automatically/dynamically) impact which analyses that are preserved from the BBPassManager and the FPPassManager for this pass structure?
Regards,
Björn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180507/d60b5721/attachment.html>
2010 Feb 12
2
[LLVMdev] [PATCH] Fix off-by-one errors in the doxygen documentation
...ger types is important here.
enum PassManagerType {
PMT_Unknown = 0,
- PMT_ModulePassManager = 1, /// MPPassManager
- PMT_CallGraphPassManager, /// CGPassManager
- PMT_FunctionPassManager, /// FPPassManager
- PMT_LoopPassManager, /// LPPassManager
- PMT_BasicBlockPassManager, /// BBPassManager
+ PMT_ModulePassManager = 1, ///< MPPassManager
+ PMT_CallGraphPassManager, ///< CGPassManager
+ PMT_FunctionPassManager, ///< FPPassManager
+ PMT_LoopPassManager, ///< LPPassManager
+ PMT_BasicBlockPassManager, ///< BBPassManager
PMT_Last
};
--
1.6.5
--
Pe...
2018 May 07
0
Preservation of CallGraph (by BasicBlockPass, FunctionPass)
...> exclude “CallGraph Construction” from the set of preserved analyses, or am I
> missing something here?
>
>
>
> I assume that DeadInstElimination isn’t preserving the CallGraph. Shouldn’t
> that (automatically/dynamically) impact which analyses that are preserved
> from the BBPassManager and the FPPassManager for this pass structure?
>
>
>
> Regards,
>
> Björn
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
2018 May 08
2
Preservation of CallGraph (by BasicBlockPass, FunctionPass)
...om the set of preserved analyses, or
> am I
> > missing something here?
> >
> >
> >
> > I assume that DeadInstElimination isn’t preserving the CallGraph. Shouldn’t
> > that (automatically/dynamically) impact which analyses that are preserved
> > from the BBPassManager and the FPPassManager for this pass structure?
> >
> >
> >
> > Regards,
> >
> > Björn
> >
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > http://list...
2018 May 08
0
Preservation of CallGraph (by BasicBlockPass, FunctionPass)
...I
> > > missing something here?
> > >
> > >
> > >
> > > I assume that DeadInstElimination isn’t preserving the CallGraph.
> Shouldn’t
> > > that (automatically/dynamically) impact which analyses that are
> preserved
> > > from the BBPassManager and the FPPassManager for this pass structure?
> > >
> > >
> > >
> > > Regards,
> > >
> > > Björn
> > >
> > >
> > > _______________________________________________
> > > LLVM Developers mailing list
> >...
2010 Mar 06
1
[LLVMdev] region pass - new pass for llvm
...ple removeS ..."
* include/llvm/LinkAllPasses.h
- PMT_ModulePassManager = 1, ///< MPPassManager
- PMT_CallGraphPassManager, ///< CGPassManager
- PMT_FunctionPassManager, ///< FPPassManager
- PMT_LoopPassManager, ///< LPPassManager
- PMT_BasicBlockPassManager, ///< BBPassManager
+ PMT_ModulePassManager = 1, /// MPPassManager
+ PMT_CallGraphPassManager, /// CGPassManager
+ PMT_FunctionPassManager, /// FPPassManager
Why do you remove the "<"? Does not seem to be related to the Region
stuff, so please submit this as a separate patch.
- virtual void *...
2015 May 06
2
[LLVMdev] (Possibly buggy?) doFinalization method behavior of FunctionPass
On 5/6/15 11:15 AM, Kuperstein, Michael M wrote:
>
> I’ve always thought that the only guarantee is that
> doFinalization(Module &M) runs after runOnFunction() was executed for
> all functions in M, and there’s no guarantee it runs *immediately* after.
>
> That is, a PM may run a bunch of function passes over each function,
> and only then call doFinazliation() for each