search for: targetlibraryanalysi

...de: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/201...

...id a quick run-through of PassRegistry.def and this is what I > found: > > Module analyses: 0/5 hold pointers to other analyses > CallGraph: No pointers to other analyses. > LazyCallGraph: No pointers to other analyses. > ProfileSummaryAnalysis: No pointers to other analyses. > TargetLibraryAnalysis: No pointers to other analyses. > VerifierAnalysis: No pointers to other analyses. > > 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 &...

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

...hat I >>> found: >>> >>> Module analyses: 0/5 hold pointers to other analyses >>> CallGraph: No pointers to other analyses. >>> LazyCallGraph: No pointers to other analyses. >>> ProfileSummaryAnalysis: No pointers to other analyses. >>> TargetLibraryAnalysis: No pointers to other analyses. >>> VerifierAnalysis: No pointers to other analyses. >>> >>> Module alias analyses: 1/1 keeps pointer to other analysis. >>> GlobalsAA: Result keeps pointer to TLI (this is a function analysis). >>> >>> Function...

...problem with multi-context execution     (callbacks can be made owning the instrumentation data). Open Questions ==============   - whats the best way to handle ownership of PassInstrumentation     Any problems with owning by LLVMContext?     Something similar to TargetLibraryInfo (owned by TargetLibraryAnalysis/TargetLibraryInfoWrapperPass)?   - using PassInstrumentationAnalysis or directly querying LLVMContext     PassInstrumentationAnalysis appeared to be a nice idea, only until I tried querying it     in new pass manager framework, and amount of hooplas to jump over makes me shiver a bit...  ...

...st did a quick run-through of PassRegistry.def and this is what I > found: > Module analyses: 0/5 hold pointers to other analyses > CallGraph: No pointers to other analyses. > LazyCallGraph: No pointers to other analyses. > ProfileSummaryAnalysis: No pointers to other analyses. > TargetLibraryAnalysis: No pointers to other analyses. > VerifierAnalysis: No pointers to other analyses. > 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 > AAM...

...gt;>>>> Module analyses: 0/5 hold pointers to other analyses >>>>> CallGraph: No pointers to other analyses. >>>>> LazyCallGraph: No pointers to other analyses. >>>>> ProfileSummaryAnalysis: No pointers to other analyses. >>>>> TargetLibraryAnalysis: No pointers to other analyses. >>>>> VerifierAnalysis: No pointers to other analyses. >>>>> >>>>> Module alias analyses: 1/1 keeps pointer to other analysis. >>>>> GlobalsAA: Result keeps pointer to TLI (this is a function analysis). &gt...

...gt; > > > > > > > LazyCallGraph: No pointers to other analyses. > > > > > > > > > > > > > > > ProfileSummaryAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > TargetLibraryAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > VerifierAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > Module alias analyses: 1/1 keeps pointer to other analysi...

...problem with multi-context execution (callbacks can be made owning the instrumentation data). Open Questions ============== - whats the best way to handle ownership of PassInstrumentation Any problems with owning by LLVMContext? Something similar to TargetLibraryInfo (owned by TargetLibraryAnalysis/TargetLibraryInfoWrapperPass)? - using PassInstrumentationAnalysis or directly querying LLVMContext PassInstrumentationAnalysis appeared to be a nice idea, only until I tried querying it in new pass manager framework, and amount of hooplas to jump over makes me shiver a bit......

...owning the instrumentation data). > > Open Questions > ============== > >    - whats the best way to handle ownership of PassInstrumentation > >      Any problems with owning by LLVMContext? >      Something similar to TargetLibraryInfo (owned by > TargetLibraryAnalysis/TargetLibraryInfoWrapperPass)? > >    - using PassInstrumentationAnalysis or directly querying > LLVMContext > >      PassInstrumentationAnalysis appeared to be a nice idea, only > until > I tried querying it >      in new pass manager framework, and...

...gt; > > > > > > > > > > > > > > > > > > ProfileSummaryAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > > > > > > > > > > > > > > TargetLibraryAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > > > > > > > > > > > > > > VerifierAnalysis: No pointers to other analyses. > > > > > > > > > > > > > &gt...

...gt; > > > > > > > > > > > > > > > > > > ProfileSummaryAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > > > > > > > > > > > > > > TargetLibraryAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > > > > > > > > > > > > > > VerifierAnalysis: No pointers to other analyses. > > > > > > > > > > > > > &gt...

...gt; > > > > > > > > > > > > > > > > > > ProfileSummaryAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > > > > > > > > > > > > > > TargetLibraryAnalysis: No pointers to other analyses. > > > > > > > > > > > > > > > > > > > > > > > > > > > > VerifierAnalysis: No pointers to other analyses. > > > > > > > > > > > > > &gt...

...gt;>>> ============== >>>> >>>> - whats the best way to handle ownership of PassInstrumentation >>>> >>>> Any problems with owning by LLVMContext? >>>> Something similar to TargetLibraryInfo (owned by >>>> TargetLibraryAnalysis/TargetLibraryInfoWrapperPass)? >>>> >>>> - using PassInstrumentationAnalysis or directly querying LLVMContext >>>> >>>> PassInstrumentationAnalysis appeared to be a nice idea, only until >>>> I tried querying it >>>>...

...gt; Module analyses: 0/5 hold pointers to other analyses >>>>>> CallGraph: No pointers to other analyses. >>>>>> LazyCallGraph: No pointers to other analyses. >>>>>> ProfileSummaryAnalysis: No pointers to other analyses. >>>>>> TargetLibraryAnalysis: No pointers to other analyses. >>>>>> VerifierAnalysis: No pointers to other analyses. >>>>>> >>>>>> Module alias analyses: 1/1 keeps pointer to other analysis. >>>>>> GlobalsAA: Result keeps pointer to TLI (this is a functio...

...ses: 0/5 hold pointers to other analyses >>>>>>> CallGraph: No pointers to other analyses. >>>>>>> LazyCallGraph: No pointers to other analyses. >>>>>>> ProfileSummaryAnalysis: No pointers to other analyses. >>>>>>> TargetLibraryAnalysis: No pointers to other analyses. >>>>>>> VerifierAnalysis: No pointers to other analyses. >>>>>>> >>>>>>> Module alias analyses: 1/1 keeps pointer to other analysis. >>>>>>> GlobalsAA: Result keeps pointer to TLI (t...

...ses: 0/5 hold pointers to other analyses >>>>>>> CallGraph: No pointers to other analyses. >>>>>>> LazyCallGraph: No pointers to other analyses. >>>>>>> ProfileSummaryAnalysis: No pointers to other analyses. >>>>>>> TargetLibraryAnalysis: No pointers to other analyses. >>>>>>> VerifierAnalysis: No pointers to other analyses. >>>>>>> >>>>>>> Module alias analyses: 1/1 keeps pointer to other analysis. >>>>>>> GlobalsAA: Result keeps pointer to TLI (t...

...- whats the best way to handle ownership of > PassInstrumentation > > Any problems with owning by LLVMContext? > Something similar to TargetLibraryInfo (owned by > TargetLibraryAnalysis/TargetLibraryInfoWrapperPass) > ? > > - using PassInstrumentationAnalysis or directly > querying LLVMContext > > PassInstrumentationAnalysis appeared to be a...

With D21921 and a couple other pending patches, we now have the full LTO pipeline converted to the new PM. I was trying it out on test-suite and SPEC2006. Yay! This email is about one issue that I ran into testing the pipeline on test-suite. The issue arose in the wild as an interaction between lcssa and gvn. But the issue is extremely general. What happened is that BasicAA uses

...analyses >>>>>>>>> CallGraph: No pointers to other analyses. >>>>>>>>> LazyCallGraph: No pointers to other analyses. >>>>>>>>> ProfileSummaryAnalysis: No pointers to other analyses. >>>>>>>>> TargetLibraryAnalysis: No pointers to other analyses. >>>>>>>>> VerifierAnalysis: No pointers to other analyses. >>>>>>>>> >>>>>>>>> Module alias analyses: 1/1 keeps pointer to other analysis. >>>>>>>>> GlobalsAA...