Displaying 4 results from an estimated 4 matches for "llvmpassmanagerbuilderref".
2013 Mar 21
2
[LLVMdev] Changing the LLVM C API to remove a pass
...ionattrs. Now I am ready to completely to remove what is
left of the pass from
the source tree. However, there are a few C API functions for
creating and managing
the pass:
/** See llvm::PassManagerBuilder::DisableSimplifyLibCalls */
void
LLVMPassManagerBuilderSetDisableSimplifyLibCalls(LLVMPassManagerBuilderRef
PMB,
LLVMBool Value);
/** See llvm::createSimplifyLibCallsPass function. */
void LLVMAddSimplifyLibCallsPass(LLVMPassManagerRef PM);
Is it OK to remove these? Do I need to keep them? Or is there some
sort of deprecation process?
-- Meador
2013 Mar 21
0
[LLVMdev] Changing the LLVM C API to remove a pass
...remove what is
> left of the pass from
> the source tree. However, there are a few C API functions for
> creating and managing
> the pass:
>
> /** See llvm::PassManagerBuilder::DisableSimplifyLibCalls */
> void
> LLVMPassManagerBuilderSetDisableSimplifyLibCalls(LLVMPassManagerBuilderRef
> PMB,
>
> LLVMBool Value);
>
> /** See llvm::createSimplifyLibCallsPass function. */
> void LLVMAddSimplifyLibCallsPass(LLVMPassManagerRef PM);
>
>
> Is it OK to remove these? Do I need to keep them? Or is there some
> sort of deprecation process?...
2013 Jul 28
0
[LLVMdev] IR Passes and TargetTransformInfo: Straw Man
...scalar chains.
+ }
+ }
+
+ if (EnableLightWeightIPO) {
+ PM.add(createGlobalDCEPass()); // Remove dead fns and globals.
+ PM.add(createConstantMergePass()); // Merge dup global constants
+ }
+ addExtensionsToPM(EP_OptimizerLast, PM);
}
inline PassManagerBuilder *unwrap(LLVMPassManagerBuilderRef P) {
@@ -458,5 +583,6 @@
LLVMBool RunInliner) {
PassManagerBuilder *Builder = unwrap(PMB);
PassManagerBase *LPM = unwrap(PM);
- Builder->populateLTOPassManager(*LPM, Internalize != 0, RunInliner != 0);
+ Builder->populateIPOPassManage...
2013 Jul 18
3
[LLVMdev] IR Passes and TargetTransformInfo: Straw Man
Andy and I briefly discussed this the other day, we have not yet got
chance to list a detailed pass order
for the pre- and post- IPO scalar optimizations.
This is wish-list in our mind:
pre-IPO: based on the ordering he propose, get rid of the inlining (or
just inline tiny func), get rid of
all loop xforms...
post-IPO: get rid of inlining, or maybe we still need it, only