projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4e4989a) | patch
[FIX] Check the next base pointer for possible invariant loads
authorJohannes Doerfert <doerfert@cs.uni-saarland.de>
Mon, 15 Feb 2016 12:42:05 +0000 (12:42 +0000)
committerJohannes Doerfert <doerfert@cs.uni-saarland.de>
Mon, 15 Feb 2016 12:42:05 +0000 (12:42 +0000)
commit4cf1580f0cd9980b28a4fa46ebcae30c107caf5e
treee44e4cf9073cbc07b5524360beecb3d19574e6fbtree | snapshot
parent4e4989a64aa5fa64855ebcffa9a07937f3cca203commit | diff
[FIX] Check the next base pointer for possible invariant loads

  A load can only be invariant if its base pointer is invariant too. To
  this end, we check if the base pointer is defined inside the region or
  outside. In the former case we recursively check if we can (and
  therefore will) hoist the base pointer too. Only if that happends we
  can hoist the load.

llvm-svn: 260886
polly/lib/Analysis/ScopInfo.cpp diff | blob | history
polly/test/Isl/CodeGen/hoisting_1.ll [new file with mode: 0644] blob
polly/test/Isl/CodeGen/hoisting_2.ll [new file with mode: 0644] blob
Domain: System / Toolchain;