summaryrefslogtreecommitdiffstats
path: root/polly/test/Isl/CodeGen/invariant_cannot_handle_void.ll
Commit message (Collapse)AuthorAgeFilesLines
* Migrate function attribute "no-frame-pointer-elim"="false" to ↵Fangrui Song2019-12-241-1/+1
| | | | "frame-pointer"="none" as cleanups after D56351
* [tests] Force invariant load hoisting for test cases that need itTobias Grosser2016-08-151-2/+2
| | | | | | | | This will make it easier to switch the default of Polly's invariant load hoisting strategy and also makes it very clear that these test cases indeed require invariant code hoisting to work. llvm-svn: 278667
* This reverts recent expression type changesTobias Grosser2016-06-111-1/+1
| | | | | | | | | | | | | | | | | | | | | The recent expression type changes still need more discussion, which will happen on phabricator or on the mailing list. The precise list of commits reverted are: - "Refactor division generation code" - "[NFC] Generate runtime checks after the SCoP" - "[FIX] Determine insertion point during SCEV expansion" - "Look through IntToPtr & PtrToInt instructions" - "Use minimal types for generated expressions" - "Temporarily promote values to i64 again" - "[NFC] Avoid unnecessary comparison for min/max expressions" - "[Polly] Fix -Wunused-variable warnings (NFC)" - "[NFC] Simplify min/max expression generation" - "Simplify the type adjustment in the IslExprBuilder" Some of them are just reverted as we would otherwise get conflicts. I will try to re-commit them if possible. llvm-svn: 272483
* Use minimal types for generated expressionsJohannes Doerfert2016-06-061-1/+1
| | | | | | | | | | | | We now use the minimal necessary bit width for the generated code. If operations might overflow (add/sub/mul) we will try to adjust the types in order to ensure a non-wrapping computation. If the type adjustment is not possible, thus the necessary type is bigger than the type value of --polly-max-expr-bit-width, we will use assumptions to verify the computation will not wrap. However, for run-time checks we cannot build assumptions but instead utilize overflow tracking intrinsics. llvm-svn: 271878
* Allow all combinations of types and subscripts for memory accessesJohannes Doerfert2016-02-181-2/+20
| | | | | | | | | | | | To support non-aligned accesses we introduce a virtual element size for arrays that divides each access function used for this array. The adjustment of the access function based on the element size of the array was therefore moved after this virtual element size was determined, thus after all accesses have been created. Differential Revision: http://reviews.llvm.org/D17246 llvm-svn: 261226
* [FIX] Bail if access function is not divisible by element size.Johannes Doerfert2015-11-121-4/+2
| | | | llvm-svn: 252942
* [FIX] Do not try to hoist "empty" accessesJohannes Doerfert2015-10-181-0/+60
Accesses that have a relative offset (in bytes) that is not divisible by the type size (in bytes) will be represented as empty in the SCoP description. This is on its own not good but it also crashed the invariant load hoisting. This patch will fix the latter problem while the former should be addressed too. This fixes bug 25236. llvm-svn: 250664
OpenPOWER on IntegriCloud