Why aren't polly.merge and entry in the same color region in the attached file? What I'm looking to do is match up a control flow to it's end merge point. This is simple to do based on preds providing each block is in an independent path; however, this is not always the case. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120215/03c7d484/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: RegionInfo_loop Type: application/octet-stream Size: 3169 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120215/03c7d484/attachment.obj>
On 02/15/2012 11:37 PM, Ryan Taylor wrote:> Why aren't polly.merge and entry in the same color region in the > attached file?Even though polly.merge terminates the green region, it is itself not part of the green region. The green region is left right before entering polly.merge. There may be other edges, that enter polly.merge but that are not part of the green region.> What I'm looking to do is match up a control flow to it's end merge > point. > This is simple to do based on preds providing each block is in an > independent path; however, this is not always the case.I do not get this paragraph. Could you try to rephrase? Cheers Tobi
Maybe Matching Threads
- [LLVMdev] Your LLVM email
- [LLVMdev] The implementation algorithm behind LLVM's RegionInfo class
- [LLVMdev] The implementation algorithm behind LLVM's RegionInfo class
- [LLVMdev] How to make Polly ignore some non-affine memory accesses
- [LLVMdev] How to make Polly ignore some non-affine memory accesses