forked from OSchip/llvm-project
4284049dcc
Summary: Without any information about the called function, we cannot be sure that it is safe to interchange loops which contain function calls. For example there could be dependences that prevent interchanging between accesses in the called function and the loops. Even functions without any parameters could cause problems, as they could access memory using global pointers. For now, I think it is only safe to interchange loops with calls marked as readnone. With this patch, the LLVM test suite passes with `-O3 -mllvm -enable-loopinterchange` and LoopInterchangeProfitability::isProfitable returning true for all loops. check-llvm and check-clang also pass when bootstrapped in a similar fashion, although only 3 loops got interchanged. Reviewers: karthikthecool, blitz.opensource, hfinkel, mcrosier, mkuper Reviewed By: mcrosier Subscribers: mzolotukhin, llvm-commits Differential Revision: https://reviews.llvm.org/D35489 llvm-svn: 309547 |
||
|---|---|---|
| .. | ||
| call-instructions.ll | ||
| current-limitations-lcssa.ll | ||
| currentLimitation.ll | ||
| interchange-flow-dep-outer.ll | ||
| interchange-not-profitable.ll | ||
| interchange-output-dependencies.ll | ||
| interchange-simple-count-down.ll | ||
| interchange-simple-count-up.ll | ||
| loop-interchange-optimization-remarks.ll | ||
| not-interchanged-dependencies-1.ll | ||
| not-interchanged-loop-nest-3.ll | ||
| not-interchanged-tightly-nested.ll | ||
| profitability.ll | ||
| reductions.ll | ||