5a4ec5c42b
Only when load-hoisted we can be sure the base pointer is invariant during the SCoP's execution. Most of the time it would be added to the required hoists for the alias checks anyway, except with -polly-ignore-aliasing, -polly-use-runtime-alias-checks=0 or if AliasAnalysis is already sure it doesn't alias with anything (for instance if there is no other pointer to alias with). Two more parts in Polly assume that this load-hoisting took place: - setNewAccessRelation() which contains an assert which tests this. - BlockGenerator which would use to the base ptr from the original code if not load-hoisted (if the access expression is regenerated) Differential Revision: https://reviews.llvm.org/D30694 llvm-svn: 297195 |
||
|---|---|---|
| .. | ||
| ReportAlias-01.ll | ||
| ReportEntry.ll | ||
| ReportFuncCall-01.ll | ||
| ReportIrreducibleRegion.ll | ||
| ReportIrreducibleRegionWithoutDebugLoc.ll | ||
| ReportLoopBound-01.ll | ||
| ReportLoopHasNoExit.ll | ||
| ReportMultipleNonAffineAccesses.ll | ||
| ReportNonAffineAccess-01.ll | ||
| ReportUnprofitable.ll | ||
| ReportUnreachableInExit.ll | ||
| ReportVariantBasePtr-01.ll | ||