forked from OSchip/llvm-project
8b05278b4e
In case we also model scalar reads it can happen that a pointer appears in both a scalar read access as well as the base pointer of an array access. As this is a little surprising, we add a specific test case to document this behaviour. To my understanding it should be OK to have a read from an array A[] and read/write accesses to A[...]. isl is treating these arrays as unrelated as their dimensionality differs. This seems to be correct as A[] remains constant throughout the execution of the scop and is not affected by the reads/writes to A[...]. If this causes confusion, it might make sense to make this behaviour more obvious by using different names (e.g., A_scalar[], A[...]). llvm-svn: 252615 |
||
|---|---|---|
| .. | ||
| DeadCodeElimination | ||
| DependenceInfo | ||
| Isl | ||
| ScheduleOptimizer | ||
| ScopDetect | ||
| ScopDetectionDiagnostics | ||
| ScopInfo | ||
| CMakeLists.txt | ||
| Makefile | ||
| README | ||
| create_ll.sh | ||
| lit.cfg | ||
| lit.site.cfg.in | ||
| polly.ll | ||
README
place tests here