forked from OSchip/llvm-project
184a4926b3
getAccessFor does not guarantee a certain access to be returned in case an instruction is related to multiple accesses. However, in the vector code generation we want to know the stride of the array access of a store instruction. By using getArrayAccessFor we ensure we always get the correct memory access. This patch fixes a potential bug, but I was unable to produce a failing test case. Several existing test cases cover this code, but all of them already passed out of luck (or the specific but not-guaranteed order in which we build memory accesses). llvm-svn: 255715 |
||
|---|---|---|
| .. | ||
| BlockGenerators.cpp | ||
| CodeGeneration.cpp | ||
| CodegenCleanup.cpp | ||
| IRBuilder.cpp | ||
| IslAst.cpp | ||
| IslExprBuilder.cpp | ||
| IslNodeBuilder.cpp | ||
| LoopGenerators.cpp | ||
| RuntimeDebugBuilder.cpp | ||
| Utils.cpp | ||