search for: p6603

...#39;re being used. > > New updated rendering at http://reviews.llvm.org/F2161258 <http://reviews.llvm.org/F2161258> (DependenceAnalysis was missing some edges in my previous rendering and I didn't have and I've added LoopAccessAnalysis; I've updated http://reviews.llvm.org/P6603 <http://reviews.llvm.org/P6603>). Which other analyses vend data objects that others might hold pointers to? > > SCEV, Loop, SCC, DomTreeNode, and Region leap immediately to mind. and 3 of those are what would be IRUnitTs (Region being the third, and its weird and likely won't be i...

...-by-case depending on how they're being used. > New updated rendering at http://reviews.llvm.org/F2161258 > (DependenceAnalysis was missing some edges in my previous rendering and I > didn't have and I've added LoopAccessAnalysis; I've updated > http://reviews.llvm.org/P6603). Which other analyses vend data objects > that others might hold pointers to? > SCEV, Loop, SCC, DomTreeNode, and Region leap immediately to mind. and 3 of those are what would be IRUnitTs (Region being the third, and its weird and likely won't be in the new PM ever). -------------- nex...

...n that makes it easy to get this right. -Hal > Since I like to visualize things, here is a quick graph of the > dependencies between analyses which hold pointers to each other. > Edge A -> B indicates "A can/does hold a pointer to B". > dot file: http://reviews.llvm.org/P6603 > rendering: http://reviews.llvm.org/F2161058 > (I've been a bit loose with terminology here. A lot of the times that > I say "analysis" I mean "the analysis' result object" or I use the > name of the analysis interchangeably with the analysis result > ob...

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