search for: assumptionanalysis

Looking at the InstructionCombining.cpp code: PreservedAnalyses InstCombinePass::run(Function &F,                                        AnalysisManager<Function> &AM) {   auto &AC = AM.getResult<AssumptionAnalysis>(F);   auto &DT = AM.getResult<DominatorTreeAnalysis>(F);   auto &TLI = AM.getResult<TargetLibraryAnalysis>(F);   auto *LI = AM.getCachedResult<LoopAnalysis>(F);   // FIXME: The AliasAnalysis is not yet supported in the new pass manager Thanks, Welson --------------...

...> > > > > > > > > > > AAManager: Its Result holds TLI pointer and pointers to > > > > > individual > > > > > AA > > > > > result objects. > > > > > > > > > > > > > > > AssumptionAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > BlockFrequencyAnalysis: Its Result holds pointers to LoopInfo > > > > > and > > > > > BPI. > > > > > > > > > > > > &...

...er and pointers to > > > > > > > individual > > > > > > > AA > > > > > > > result objects. > > > > > > > > > > > > > > > > > > > > > > > > > > > > AssumptionAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > > > > > > > > > > > > > > BlockFrequencyAnalysis: Its Result holds pointers to > > > > > > > LoopInfo > > > > &gt...

...er and pointers to > > > > > > > individual > > > > > > > AA > > > > > > > result objects. > > > > > > > > > > > > > > > > > > > > > > > > > > > > AssumptionAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > > > > > > > > > > > > > > BlockFrequencyAnalysis: Its Result holds pointers to > > > > > > > LoopInfo > > > > &gt...

...I (this is a function analysis). >>>>>> >>>>>> Function analyses: 9/17 keep pointers to other analysis >>>>>> AAManager: Its Result holds TLI pointer and pointers to individual AA >>>>>> result objects. >>>>>> AssumptionAnalysis: No pointers to other analyses. >>>>>> BlockFrequencyAnalysis: Its Result holds pointers to LoopInfo and BPI. >>>>>> BranchProbabilityAnalysis: Stores no pointers to other analyses. >>>>>> (uses LoopInfo to "recalculate" though) >&g...

...n analysis). >>>>>>> >>>>>>> Function analyses: 9/17 keep pointers to other analysis >>>>>>> AAManager: Its Result holds TLI pointer and pointers to individual >>>>>>> AA result objects. >>>>>>> AssumptionAnalysis: No pointers to other analyses. >>>>>>> BlockFrequencyAnalysis: Its Result holds pointers to LoopInfo and >>>>>>> BPI. >>>>>>> BranchProbabilityAnalysis: Stores no pointers to other analyses. >>>>>>> (uses LoopInfo...

...analysis. >>> GlobalsAA: Result keeps pointer to TLI (this is a function analysis). >>> >>> Function analyses: 9/17 keep pointers to other analysis >>> AAManager: Its Result holds TLI pointer and pointers to individual AA >>> result objects. >>> AssumptionAnalysis: No pointers to other analyses. >>> BlockFrequencyAnalysis: Its Result holds pointers to LoopInfo and BPI. >>> BranchProbabilityAnalysis: Stores no pointers to other analyses. (uses >>> LoopInfo to "recalculate" though) >>> DominatorTreeAnalysis: Stores...

...able > restriction? What's the potential use case for getting an analysis outside of something in, or called by, run()? > One annoying problem is that I think that the dependency links will > need to be bidirectional. To use the example analysis cache from my > other post: > (AssumptionAnalysis, function @bar) -> (AssumptionCache for @bar, > [(SomeModuleAnalysis, module TheModule)]) > (AssumptionAnalysis, function @baz) -> (AssumptionCache for @baz, > [(SomeModuleAnalysis, module TheModule)]) > (SomeModuleAnalysis, module TheModule) -> (SomeModuleAnalysisResult > f...

...keeps pointer to TLI (this is a function analysis). >>>>> >>>>> Function analyses: 9/17 keep pointers to other analysis >>>>> AAManager: Its Result holds TLI pointer and pointers to individual AA >>>>> result objects. >>>>> AssumptionAnalysis: No pointers to other analyses. >>>>> BlockFrequencyAnalysis: Its Result holds pointers to LoopInfo and BPI. >>>>> BranchProbabilityAnalysis: Stores no pointers to other analyses. (uses >>>>> LoopInfo to "recalculate" though) >>>>&g...

...o that the dependencies are implicitly tracked via re-entrance > to get{,Cached}Result); is this a reasonable restriction? > > > One annoying problem is that I think that the dependency links will need > to be bidirectional. To use the example analysis cache from my other post: > (AssumptionAnalysis, function @bar) -> (AssumptionCache for @bar, > [(SomeModuleAnalysis, module TheModule)]) > (AssumptionAnalysis, function @baz) -> (AssumptionCache for @baz, > [(SomeModuleAnalysis, module TheModule)]) > (SomeModuleAnalysis, module TheModule) -> (SomeModuleAnalysisResult for &g...

...dule alias analyses: 1/1 keeps pointer to other analysis. > GlobalsAA: Result keeps pointer to TLI (this is a function analysis). > > Function analyses: 9/17 keep pointers to other analysis > AAManager: Its Result holds TLI pointer and pointers to individual AA > result objects. > AssumptionAnalysis: No pointers to other analyses. > BlockFrequencyAnalysis: Its Result holds pointers to LoopInfo and BPI. > BranchProbabilityAnalysis: Stores no pointers to other analyses. (uses > LoopInfo to "recalculate" though) > DominatorTreeAnalysis: Stores no pointers to other analyses....

...ia re-entrance >>> to get{,Cached}Result); is this a reasonable restriction? >>> >>> >>> One annoying problem is that I think that the dependency links will need >>> to be bidirectional. To use the example analysis cache from my other post: >>> (AssumptionAnalysis, function @bar) -> (AssumptionCache for @bar, >>> [(SomeModuleAnalysis, module TheModule)]) >>> (AssumptionAnalysis, function @baz) -> (AssumptionCache for @baz, >>> [(SomeModuleAnalysis, module TheModule)]) >>> (SomeModuleAnalysis, module TheModule) ->...

On Tue, Jul 12, 2016 at 11:34 PM Sean Silva <chisophugis at gmail.com> wrote: > On Tue, Jul 12, 2016 at 11:32 PM, Xinliang David Li <davidxl at google.com> > wrote: > >> >> >> On Tue, Jul 12, 2016 at 10:57 PM, Chandler Carruth <chandlerc at gmail.com> >> wrote: >> >>> Yea, this is a nasty problem. >>> >>> One

...ached}Result); is this a reasonable restriction? >>>> >>>> >>>> One annoying problem is that I think that the dependency links will >>>> need to be bidirectional. To use the example analysis cache from my other >>>> post: >>>> (AssumptionAnalysis, function @bar) -> (AssumptionCache for @bar, >>>> [(SomeModuleAnalysis, module TheModule)]) >>>> (AssumptionAnalysis, function @baz) -> (AssumptionCache for @baz, >>>> [(SomeModuleAnalysis, module TheModule)]) >>>> (SomeModuleAnalysis, module T...

...reasonable restriction? >>>>> >>>>> >>>>> One annoying problem is that I think that the dependency links will >>>>> need to be bidirectional. To use the example analysis cache from my other >>>>> post: >>>>> (AssumptionAnalysis, function @bar) -> (AssumptionCache for @bar, >>>>> [(SomeModuleAnalysis, module TheModule)]) >>>>> (AssumptionAnalysis, function @baz) -> (AssumptionCache for @baz, >>>>> [(SomeModuleAnalysis, module TheModule)]) >>>>> (SomeModuleAn...

...; Module alias analyses: 1/1 keeps pointer to other analysis. > GlobalsAA: Result keeps pointer to TLI (this is a function analysis). > Function analyses: 9/17 keep pointers to other analysis > AAManager: Its Result holds TLI pointer and pointers to individual AA > result objects. > AssumptionAnalysis: No pointers to other analyses. > BlockFrequencyAnalysis: Its Result holds pointers to LoopInfo and > BPI. > BranchProbabilityAnalysis: Stores no pointers to other analyses. > (uses LoopInfo to "recalculate" though) > DominatorTreeAnalysis: Stores no pointers to other an...

...tracked via re-entrance to get{,Cached}Result); is this a reasonable restriction? >>>> >>>> >>>> One annoying problem is that I think that the dependency links will need to be bidirectional. To use the example analysis cache from my other post: >>>> (AssumptionAnalysis, function @bar) -> (AssumptionCache for @bar, [(SomeModuleAnalysis, module TheModule)]) >>>> (AssumptionAnalysis, function @baz) -> (AssumptionCache for @baz, [(SomeModuleAnalysis, module TheModule)]) >>>> (SomeModuleAnalysis, module TheModule) -> (SomeModuleAnalysi...