diff options
author | Eli Friedman <efriedma@codeaurora.org> | 2018-09-11 23:48:14 +0000 |
---|---|---|
committer | Eli Friedman <efriedma@codeaurora.org> | 2018-09-11 23:48:14 +0000 |
commit | efe18d3977c29074bfdcb5dc13da0ed2c3b1f86e (patch) | |
tree | cea04c20a8c7acfa6ed9afb0eeb38c26e50e5e7c /llvm/lib/Transforms/Utils/LoopUtils.cpp | |
parent | 2386eab3600f639fb116a7e7e6f189b6c7b5accb (diff) | |
download | llvm-efe18d3977c29074bfdcb5dc13da0ed2c3b1f86e.zip llvm-efe18d3977c29074bfdcb5dc13da0ed2c3b1f86e.tar.gz llvm-efe18d3977c29074bfdcb5dc13da0ed2c3b1f86e.tar.bz2 |
[ScopDetection] Use addUnknown for calls in the AliasSetTracker.
The general-purpose add() now sometimes adds unexpected loop-variant
pointers to the AliasSetTracker, so certain loops would be rejected with
-polly-allow-modref-calls. Use addUnknown() instead, which has the old
behavior.
I'm not completely convinced the resulting behavior is actually
correct: ScopDetection::isValidAccess seems to mostly ignore
"unknown" instructions in the AliasSetTracker. But it's not any worse
than what was happening before.
Committing without pre-commit review to unbreak the buildbots; the
following tests were failing:
test/ScopInfo/mod_ref_access_pointee_arguments.ll
test/ScopInfo/mod_ref_read_pointee_arguments.ll
test/ScopInfo/multidim_2d_with_modref_call_2.ll
llvm-svn: 342010
Diffstat (limited to 'llvm/lib/Transforms/Utils/LoopUtils.cpp')
0 files changed, 0 insertions, 0 deletions