summaryrefslogtreecommitdiffstats
path: root/clang/lib/Analysis/ReachableCode.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2017-01-27 10:27:32 +0000
committerChandler Carruth <chandlerc@gmail.com>2017-01-27 10:27:32 +0000
commitfd2d7c72fcfd25621518a410f93711801f1f7c25 (patch)
tree6016a876063d55a78a8101b6b587b35875f9e775 /clang/lib/Analysis/ReachableCode.cpp
parentfa37b18f9406c33cda01e0d60bbec6d20e20682a (diff)
downloadbcm5719-llvm-fd2d7c72fcfd25621518a410f93711801f1f7c25.tar.gz
bcm5719-llvm-fd2d7c72fcfd25621518a410f93711801f1f7c25.zip
[LICM] When we are recomputing the alias sets for a subloop, we cannot
skip sub-subloops. The logic to skip subloops dated from when this code was shared with the cached case. Once it was factored out to only run in the case of recomputed subloops it became a dangerous bug. If a subsubloop contained an interfering instruction it would be silently skipped from the alias sets for LICM. With the old pass manager this was extremely hard to trigger as it would require failing to visit these subloops with the LICM pass but then visiting the outer loop somehow. I've not yet contrived any test case that actually manages to trigger this. But with the new pass manager we don't do the cross-loop caching hack that the old PM does and so we recompute alias set information from first principles. While this seems much cleaner and simpler it exposed this bug and would subtly miscompile code due to failing to correctly model the aliasing constraints of deeply nested loops. llvm-svn: 293273
Diffstat (limited to 'clang/lib/Analysis/ReachableCode.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud