projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: fef609f) | patch
[FIX] Do not create a SCoP in the presence of infinite loops
authorJohannes Doerfert <doerfert@cs.uni-saarland.de>
Sun, 3 Apr 2016 23:09:06 +0000 (23:09 +0000)
committerJohannes Doerfert <doerfert@cs.uni-saarland.de>
Sun, 3 Apr 2016 23:09:06 +0000 (23:09 +0000)
commitd5edbd61a15b5416b9d10dbb4cb058a7493af75d
treeb169d7b668dc5dc3022d8c4a378097fe32a5188atree | snapshot
parentfef609f15e09b4c42334a8ff8c2de29af502ff56commit | diff
[FIX] Do not create a SCoP in the presence of infinite loops

  If a loop has no exiting blocks the region covering we use during
  schedule genertion might not cover that loop properly. For now we bail
  out as we would not optimize these loops anyway.

llvm-svn: 265280
polly/lib/Analysis/ScopDetection.cpp diff | blob | history
polly/lib/Analysis/ScopInfo.cpp diff | blob | history
polly/test/ScopInfo/schedule-constuction-endless-loop1.ll [new file with mode: 0644] blob
polly/test/ScopInfo/schedule-constuction-endless-loop2.ll [new file with mode: 0644] blob
polly/test/ScopInfo/two-loops-one-infinite.ll diff | blob | history
Domain: System / Toolchain;