search for: insertlifetime

...--===// #include "llvm/Transforms/IPO/InlinerPass.h"+#include "llvm/Analysis/LoopInfo.h" #include "llvm/ADT/SmallPtrSet.h" #include "llvm/ADT/Statistic.h" #include "llvm/Analysis/AliasAnalysis.h"@@ -58,6 +59,7 @@ Inliner::Inliner(char &ID, bool InsertLifetime) void Inliner::getAnalysisUsage(AnalysisUsage &AU) const { AU.addRequired<AssumptionCacheTracker>(); AU.addRequired<TargetLibraryInfoWrapperPass>();+ AU.addRequired<LoopInfoWrapperPass>(); getAAResultsAnalysisUsage(AU); CallGraphSCCPass::getAnalysisUsage(AU);} I get l...

> On Aug 18, 2014, at 3:09 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >> Some passes take options directly in the constructor. For example >> >> Inliner::Inliner(char &ID, int Threshold, bool InsertLifetime) >> >> Maybe we could just say that there are two different types of options. >> The ones we want to expose to users and the ones which we use for >> testing llvm itself. The options we want to expose should be just >> constructor arguments. With that distinction we s...

...ransforms/IPO/InlinerPass.h" > +#include "llvm/Analysis/LoopInfo.h" > #include "llvm/ADT/SmallPtrSet.h" > #include "llvm/ADT/Statistic.h" > #include "llvm/Analysis/AliasAnalysis.h" > @@ -58,6 +59,7 @@ Inliner::Inliner(char &ID, bool InsertLifetime) > void Inliner::getAnalysisUsage(AnalysisUsage &AU) const { > AU.addRequired<AssumptionCacheTracker>(); > AU.addRequired<TargetLibraryInfoWrapperPass>(); > + AU.addRequired<LoopInfoWrapperPass>(); > getAAResultsAnalysisUsage(AU); > CallGraphSCC...

...gt; >>>> On Aug 18, 2014, at 3:09 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >>>> >>>> Some passes take options directly in the constructor. For example >>>> >>>> Inliner::Inliner(char &ID, int Threshold, bool InsertLifetime) >>>> >>>> Maybe we could just say that there are two different types of options. >>>> The ones we want to expose to users and the ones which we use for >>>> testing llvm itself. The options we want to expose should be just >>>> construct...

...ee_div_zero_check(long long z) but that only added the keyword "alwaysinline" to the klee_div_zero_check() function in the LLVM bitcode module, it didn't do any actual inlining. I see the LLVM API has the function llvm::InlineFunction(CallInst *CI, InlineFunctionInfo &IFI, bool InsertLifetime) Should I be using this to inline all calls in a module to a particular function or is there a better way? If so what is IFI supposed to be set to? 2. I want to duplicated the debug (filename and line number information) on the division instruction (e.g. SDiv) onto every instruction (including th...

...feel right because the biggest consumer of option >> data is the passes, and you can use a single pass manager with multiple >> contexts. >> > > Some passes take options directly in the constructor. For example > > Inliner::Inliner(char &ID, int Threshold, bool InsertLifetime) > > Maybe we could just say that there are two different types of options. > The ones we want to expose to users and the ones which we use for > testing llvm itself. The options we want to expose should be just > constructor arguments. With that distinction we should be able to jus...

...l.espindola at gmail.com <mailto:rafael.espindola at gmail.com>> wrote: >>>>>> >>>>>> Some passes take options directly in the constructor. For example >>>>>> >>>>>> Inliner::Inliner(char &ID, int Threshold, bool InsertLifetime) >>>>>> >>>>>> Maybe we could just say that there are two different types of options. >>>>>> The ones we want to expose to users and the ones which we use for >>>>>> testing llvm itself. The options we want to expose should be...

Today command line arguments in LLVM are global variables. An example argument from Scalarizer.cpp is: static cl::opt<bool> ScalarizeLoadStore ("scalarize-load-store", cl::Hidden, cl::init(false), cl::desc("Allow the scalarizer pass to scalarize loads and store")); This poses a problem for clients of LLVM that aren’t traditional compilers (i.e. WebKit, and Mesa).