search for: disableintern

Hi, I need to add switches like -disable-mem2reg, disable-gvn to llvm-ld. Currently CreateStandardLTOPasses takes in only DisableInternalize and DisableInliner switches. Is modifying this API okay for these new switches, or is it doable in some other ways ? - Sanjiv

Chris Lattner wrote: > On Feb 9, 2010, at 7:39 PM, Sanjiv Gupta wrote: > > >> Hi, >> I need to add switches like -disable-mem2reg, disable-gvn to llvm-ld. >> Currently CreateStandardLTOPasses takes in only DisableInternalize and >> DisableInliner switches. >> >> Is modifying this API okay for these new switches, or is it doable in >> some other ways ? >> > > Why do you want this? > > -Chris > Mem2Reg isn't really useful for a single register machine as our...

On Feb 9, 2010, at 7:39 PM, Sanjiv Gupta wrote: > Hi, > I need to add switches like -disable-mem2reg, disable-gvn to llvm-ld. > Currently CreateStandardLTOPasses takes in only DisableInternalize and > DisableInliner switches. > > Is modifying this API okay for these new switches, or is it doable in > some other ways ? Why do you want this? -Chris

..., at 8:57 AM, Sanjiv Gupta wrote: > Chris Lattner wrote: >> On Feb 9, 2010, at 7:39 PM, Sanjiv Gupta wrote: >> >> >>> Hi, >>> I need to add switches like -disable-mem2reg, disable-gvn to llvm-ld. >>> Currently CreateStandardLTOPasses takes in only DisableInternalize and >>> DisableInliner switches. >>> >>> Is modifying this API okay for these new switches, or is it doable in >>> some other ways ? >>> >> >> Why do you want this? >> >> -Chris >> > Mem2Reg isn't really u...

...<const PassInfo*, bool, > + FilteredPassNameParser<PassInfo::Optimization> > > +OptimizationList(cl::desc("Optimizations available:")); > + > // Optimization Options > > enum OptimizationLevels { > @@ -72,9 +80,10 @@ > cl::aliasopt(DisableInternalize), > cl::desc("Alias for -disable-internalize")); > > -static cl::list<std::string> LoadableModules("load", > +//disambiguate with -load option from llvm/Support/PluginLoader.h > +/*static cl::list<std::string> LoadableModules("load"...

...); +} + static void AddStandardLinkPasses(PassManagerBase &PM) { PM.add(createVerifierPass()); // Verify that input is correct @@ -480,8 +502,9 @@ if (DisableOptimizations) return; PassManagerBuilder Builder; - Builder.populateLTOPassManager(PM, /*Internalize=*/ !DisableInternalize, + Builder.populateIPOPassManager(PM, /*Internalize=*/ !DisableInternalize, /*RunInliner=*/ !DisableInline); + Builder.populatePostIPOPM(PM); } //===----------------------------------------------------------------------===// @@ -778,6 +801,12 @@ Sta...

Hi, Reid Spencer wrote: >> That's interesting! So, one only needs to add a 2-arg function called >> RunOptimizations to the module (can't check it right now)? >> > > That is correct. That function and only that function will be called. > What happens in that function is up to you :) > So, I tried this the last two days, but to no avail. I first

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