Displaying 4 results from an estimated 4 matches for "regiontree".
[LLVMdev] Add a function splitting pass to LLVM which extracts cold regions into their own functions
2012 May 21
1
[LLVMdev] Add a function splitting pass to LLVM which extracts cold regions into their own functions
...as it uses the DominanceFrontier analysis. However, for me it works surprisingly well.
> When I committed it I tested it on the LLVM test suite, polyhedron.com and the SPEC 2006 benchmarks [1]. I got the following timings (in seconds):
>
> Name DomTree PostDomTree DomFrontier RegionTree
> SPEC 2006 1.109 0.911 0.525 0.662
> Polyhedron.com 0.034 0.029 0.016 0.022
>
> On these examples DomFrontier and RegionTree calculation is very fast. Also, I used RegionInfo for over two years in my daily Polly work. And I know people who test P...
2014 Feb 06
2
[LLVMdev] The implementation algorithm behind LLVM's RegionInfo class
Hi fellows,
I am writing to ask what is the algorithm implemented in LLVM's
RegionInfo.h/cpp. In the header file "RegionInfo.h", it says "Calculates a
program structure tree built out of single entry single exit regions
(defined in a 1994 paper called "The Program Structure Tree"). ... ... The
algorithm to calculate these data structures however is COMPLETELY
2011 Feb 03
1
[LLVMdev] Preserve RegionInfo after regionsimplify
Hi Tobias,
My RegionSimplify pass adds new exit node for refined regions to convert
them into simple region.
However, the RegionInfo pass does not seem to recognize those changes.
For example, in the attached file, bb4.region is supposed to be in the first
region.
My RegionExtractor pass required the extracted region to be simple.
Should we modify RegionInfo or is their away to preserve the
2014 Feb 06
2
[LLVMdev] The implementation algorithm behind LLVM's RegionInfo class
...iling list and asked for advice people
> (including Chris) strongly suggested to rely on existing analysis as much
> as possible. The RegionInfo pass does this by using the DominatorTree as
> well as a couple of other analysis. My measurements
> at that time have shown that building the RegionTree itself is in average
> twice as fast as building the dominator tree. The other necessary analysis
> have taken time comparable to a dominator tree construction. The use of
> DominanceFrontier in the RegionInfo tree has
> been a point criticized because this analysis is normally not used...