summaryrefslogtreecommitdiffstats
path: root/llvm/tools/llvm-objdump/llvm-objdump.h
diff options
context:
space:
mode:
authorMichael Kruse <llvm@meinersbur.de>2016-01-26 13:33:27 +0000
committerMichael Kruse <llvm@meinersbur.de>2016-01-26 13:33:27 +0000
commitee6a4fc680d64a12b5cdcd716d660c244a672a6d (patch)
treeabd0d37fb2cda1d4c46a14b2395252ccdd2f3fc0 /llvm/tools/llvm-objdump/llvm-objdump.h
parentad28e5a5897b523cc57e7a2d21a48773d0c0bc33 (diff)
downloadbcm5719-llvm-ee6a4fc680d64a12b5cdcd716d660c244a672a6d.tar.gz
bcm5719-llvm-ee6a4fc680d64a12b5cdcd716d660c244a672a6d.zip
Unique phi write accesses
Ensure that there is at most one phi write access per PHINode and ScopStmt. In particular, this would be possible for non-affine subregions with multiple exiting blocks. We replace multiple MAY_WRITE accesses by one MUST_WRITE access. The written value is constructed using a PHINode of all exiting blocks. The interpretation of the PHI WRITE's "accessed value" changed from the incoming value to the PHI like for PHI READs since there is no unique incoming value. Because region simplification shuffles around PHI nodes -- particularly with exit node PHIs -- the PHINodes at analysis time does not always exist anymore in the code generation pass. We instead remember the incoming block/value pair in the MemoryAccess. Differential Revision: http://reviews.llvm.org/D15681 llvm-svn: 258809
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud