search for: regionpassmanager

...of how to > > proceed. To this end, I will give you my personal road map that might be > > a good start for the proposal too, though it is not the only way we > > could do this: > > > > 1) Make ScopInfo & DependenceInfo function passes to avoid the > > RegionPassManager for these Polly analysis parts. [This doesn't > > need to be the first step but it should be done at some point.] > > 2) Create a secondary ScopDetection & ScopInfo that is restricted to > > analyze a single loop. We might just create a dummy region for this &g...

...s at EuroLLVM last week, I hope to have a fairly good idea of how to proceed. To this end, I will give you my personal road map that might be a good start for the proposal too, though it is not the only way we could do this: 1) Make ScopInfo & DependenceInfo function passes to avoid the RegionPassManager for these Polly analysis parts. [This doesn't need to be the first step but it should be done at some point.] 2) Create a secondary ScopDetection & ScopInfo that is restricted to analyze a single loop. We might just create a dummy region for this loop and use the original S...

.... Patches have been accepted and committed. 2. Implemented two new function passes in Polly namely ScopInfoWrapperPass ( D20962 <http://reviews.llvm.org/D20962>) and DependenceInfoWrapperPass ( D21105 <http://reviews.llvm.org/D21105>). These are required to bypass the RegionPassManager. 1. ScopInfoWrapperPass addresses creating SCoP objects for the whole function. 2. DependenceInfoWrapperPass addresses constructing polyhedral dependences for all the SCoP objects of a function. 3. These patches are currently under review and I am incorp...

...pe to have a fairly good idea of how to > proceed. To this end, I will give you my personal road map that might be > a good start for the proposal too, though it is not the only way we > could do this: > > 1) Make ScopInfo & DependenceInfo function passes to avoid the > RegionPassManager for these Polly analysis parts. [This doesn't > need to be the first step but it should be done at some point.] > 2) Create a secondary ScopDetection & ScopInfo that is restricted to > analyze a single loop. We might just create a dummy region for this > loop an...

...": > > if we want to integrate region analysis and optimization framework into > llvm, i think we can use an approach that similar to loop analysis and > optimization: write a class "regionpass" inherit from "pass", and the > corresponding pass manger "RegionPassManager". (a kind of function pass) > if we follow this approach, we need to push the region pass manager into > the llvm pass manager stack. > the first question of this approach is, whats the relationship between > "loop pass manager" and "region pass manager"? >...

...o this end, I will give you my personal road map that might > be > > > a good start for the proposal too, though it is not the only way we > > > could do this: > > > > > > 1) Make ScopInfo & DependenceInfo function passes to avoid the > > > RegionPassManager for these Polly analysis parts. [This doesn't > > > need to be the first step but it should be done at some point.] > > > 2) Create a secondary ScopDetection & ScopInfo that is restricted to > > > analyze a single loop. We might just create a dummy reg...

...you my personal road map that might >> be >> > > a good start for the proposal too, though it is not the only way we >> > > could do this: >> > > >> > > 1) Make ScopInfo & DependenceInfo function passes to avoid the >> > > RegionPassManager for these Polly analysis parts. [This doesn't >> > > need to be the first step but it should be done at some point.] >> > > 2) Create a secondary ScopDetection & ScopInfo that is restricted to >> > > analyze a single loop. We might just create...

On 01/08/10 14:20, ether wrote: > sorry that i forgot to change the subjuect > > > hi all, Hi ether, now a kind of more complete answer. > On 2010-1-7 0:11, John Mosby wrote: >> In LLVM we could add support for generalized CFG regions and >> RegionPasses. A region is a part of the CFG. The only information we >> have is, that it has one entry and one exit, this

...on into a function. The idea is similar to extracting a loop in LoopExtractor.cpp. Basically, for each region that meet our criteria, 1. Find all basic blocks in that regions 2. Call llvm::ExtractCodeRegion() to replace that region by a call to the extracted function. 3. Delete the region from the RegionPassManager queue 4. Update the RegionInfo to reflect the change To find all basic blocks (step 1), I use Region::block_iterator(). However, after changing the CFG, that block_iterator does not seem to work anymore. Should I add a list of basic blocks for each Region like what people did with Loop? Thank yo...

...want to integrate region analysis and optimization framework into >>> llvm, i think we can use an approach that similar to loop analysis and >>> optimization: write a class "regionpass" inherit from "pass", and the >>> corresponding pass manger "RegionPassManager". (a kind of function pass) >>> if we follow this approach, we need to push the region pass manager into >>> the llvm pass manager stack. >>> the first question of this approach is, whats the relationship between >>> "loop pass manager" and "r...

Why not use the "standard" algorithm for detecting SESE-regions and building a program structure tree? It should handle everything you want. It also becomes much simpler to specify a connected SESE-region by entry/exit edges, while a disconnected region is specified by entry/exit blocks. Only defining regions on blocks is not enough to be able to quickly determine how to replace/move a