Displaying 3 results from an estimated 3 matches for "loop_exit28".
Did you mean:
loop_exit
2013 Sep 25
0
[LLVMdev] [Polly] Move Polly's execution later
...ock. When Polly detects a valid loop for Polyhedral transformations, it usually introduces a new basic block "polly.merge_new_and_old" after the original loop exit block. This new basic block contains a branch instruction that decides whether to exit or re-enter the loop like this:
polly.loop_exit28: ; preds = %polly.stmt.for.body.i, %polly.loop_if25
br label %polly.merge_new_and_old
polly.merge_new_and_old: ; preds = %polly.loop_exit28, %for.body.i
...
%cmp = icmp slt i32 %2, 0
...
br i1 %cmp, label %for.body, label %for.end12...
2013 Sep 25
3
[LLVMdev] [Polly] Move Polly's execution later
...Polly detects a valid loop for Polyhedral transformations, it usually introduces a new basic block "polly.merge_new_and_old" after the original loop exit block. This new basic block contains a branch instruction that decides whether to exit or re-enter the loop like this:
>
> polly.loop_exit28: ; preds = %polly.stmt.for.body.i, %polly.loop_if25
> br label %polly.merge_new_and_old
> polly.merge_new_and_old: ; preds = %polly.loop_exit28, %for.body.i
> ...
> %cmp = icmp slt i32 %2, 0
> ...
> br i1 %cmp,...
2013 Sep 22
4
[LLVMdev] [Polly] Move Polly's execution later
Hi Tobias,
At 2013-09-19 22:59:25,"Tobias Grosser" <tobias at grosser.es> wrote:
>On 09/19/2013 04:46 PM, Star Tan wrote:
>> Hi Tobias,
>>
>>
>> I am trying to move Polly later.
>>
>>
>> LLVM provides some predefined ExtensionPointTy:
>> EP_EarlyAsPossible,
>> EP_ModuleOptimizerEarly,
>>