projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 7dcceb8) | patch
[FIX] Do not create two SAI objects for exit PHIs
authorJohannes Doerfert <doerfert@cs.uni-saarland.de>
Sun, 3 Apr 2016 11:16:00 +0000 (11:16 +0000)
committerJohannes Doerfert <doerfert@cs.uni-saarland.de>
Sun, 3 Apr 2016 11:16:00 +0000 (11:16 +0000)
commit2075b5d2a122a3790c05ce12941a738da1a8b205
tree44d33225b5f5da0ff78c54046afe83ef8d2a6cfctree | snapshot
parent7dcceb82e9b9799e620923ea05a47f6eb47a3ddacommit | diff
[FIX] Do not create two SAI objects for exit PHIs

  If an exit PHI is written and also read in the SCoP we should not create two
  SAI objects but only one. As the read is only modeled to ensure OpenMP code
  generation knows about it we can simply use the EXIT_PHI MemoryKind for both
  accesses.

llvm-svn: 265261
polly/lib/Analysis/ScopInfo.cpp diff | blob | history
polly/test/ScopInfo/exit-phi-1.ll [new file with mode: 0644] blob
Domain: System / Toolchain;