Displaying 3 results from an estimated 3 matches for "bug17323".
2013 Sep 30
0
[LLVMdev] [Polly] Move Polly's execution later
...will produce
incorrect code if we run a very simple command:
$ opt -load LLVMPolly.so -basicaa -mem2reg -polly-codegen -loop-simplify -print-module foo.preopt.ll
The output LLVM IR code would contain a exit basic block that is incorrectly
marked as "unreachable".
I have updated the bug17323 (http://llvm.org/bugs/show_bug.cgi?id=17323)
for the further debugging.
Star Tan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130930/3278805a/attachment.html>
-------------- next part --------------
A...
2013 Oct 03
1
[LLVMdev] [Polly] Move Polly's execution later
...if we run a very simple command:
> $ opt -load LLVMPolly.so -basicaa -mem2reg -polly-codegen -loop-simplify -print-module foo.preopt.ll
>
> The output LLVM IR code would contain a exit basic block that is incorrectly
> marked as "unreachable".
>
> I have updated the bug17323 (http://llvm.org/bugs/show_bug.cgi?id=17323)
> for the further debugging.
The problem is that at some point we failt to properly update the
LoopInfo. I updated the bug report with more details.
Tobias
2013 Sep 25
3
[LLVMdev] [Polly] Move Polly's execution later
On 09/25/2013 04:55 AM, Star Tan wrote:
> Here is an update about moving Polly later.
Hi star tan,
thanks for your report.
>
> 1. Why does Polly generate incorrect code when we move Polly immediately after the loop rotating pass?
>
> It is mainly caused by a wrong polly merge block. When Polly detects a valid loop for Polyhedral transformations, it usually introduces a new basic