summaryrefslogtreecommitdiffstats
path: root/llvm/test/Bitcode/compatibility-3.6.ll
diff options
context:
space:
mode:
authorTobias Grosser <tobias@grosser.es>2015-09-24 20:59:59 +0000
committerTobias Grosser <tobias@grosser.es>2015-09-24 20:59:59 +0000
commitda95a4a7c73546efdfa769a3276ca6e603278eca (patch)
tree04c9cc52cca1a5923fce450f611f2d6ba8275489 /llvm/test/Bitcode/compatibility-3.6.ll
parent4405d5d8890073a3d4a54c3dd6c6bbb86b7e4e9e (diff)
downloadbcm5719-llvm-da95a4a7c73546efdfa769a3276ca6e603278eca.tar.gz
bcm5719-llvm-da95a4a7c73546efdfa769a3276ca6e603278eca.zip
Handle read-only scalars used in PHI-nodes correctly
This change addresses three issues: - Read only scalars that enter a PHI node through an edge that comes from outside the scop are not modeled any more, as such PHI nodes will always be initialized to this initial value right before the SCoP is entered. - For PHI nodes that depend on a scalar value that is defined outside the scop, but where the scalar values is passed through an edge that itself comes from a BB that is part of the region, we introduce in this basic block a read of the out-of-scop value to ensure it's value is available to write it into the PHI alloc location. - Read only uses of scalars by PHI nodes are ignored in the general read only handling code, as they are taken care of by the general PHI node modeling code. llvm-svn: 248535
Diffstat (limited to 'llvm/test/Bitcode/compatibility-3.6.ll')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud