Displaying 3 results from an estimated 3 matches for "exit_block6_crit_edg".
Did you mean:
exit_block6_crit_edge
2013 Jul 05
0
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
...t* %22, align 4
%24 = getelementptr inbounds float* %10, i64 %.sum
%25 = load float* %24, align 4
%26 = fadd float %23, %25
store float %26, float* %21, align 4
%next_index = add i32 %next_index10, 1
%27 = icmp slt i32 %next_index, %16
br i1 %27, label %code_block8, label %exec_block4.exit_block6_crit_edge
exec_block.return_crit_edge: ; preds = %exit_block6
br label %return
return: ; preds = %exec_block.return_crit_edge, %block_code
ret void
}
2013 Jul 05
2
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
Le 5 juil. 2013 à 04:11, Tobias Grosser <tobias at grosser.es> a écrit :
> On 07/04/2013 01:39 PM, Stéphane Letz wrote:
>> Hi,
>>
>> Our DSL can generate C or directly generate LLVM IR. With LLVM 3.3, we can vectorize the C produced code using clang with -O3, or clang with -O1 then opt -O3 -vectorize-loops. But the same program generating LLVM IR version cannot be
2013 Jul 05
2
[LLVMdev] Enabling vectorization with LLVM 3.3 for a DSL emitting LLVM IR
...getelementptr inbounds float* %10, i64 %.sum
> %25 = load float* %24, align 4
> %26 = fadd float %23, %25
> store float %26, float* %21, align 4
> %next_index = add i32 %next_index10, 1
> %27 = icmp slt i32 %next_index, %16
> br i1 %27, label %code_block8, label %exec_block4.exit_block6_crit_edge
>
> exec_block.return_crit_edge: ; preds = %exit_block6
> br label %return
>
> return: ; preds = %exec_block.return_crit_edge, %block_code
> ret void
> }
>
1) "entry" block is the first block of...