diff options
| author | Tobias Grosser <tobias@grosser.es> | 2015-11-10 16:23:30 +0000 |
|---|---|---|
| committer | Tobias Grosser <tobias@grosser.es> | 2015-11-10 16:23:30 +0000 |
| commit | 8b05278b4ebbce338fbd5604340a64dab6c8d415 (patch) | |
| tree | 8ef39e34f774fca3572938f061518b63968ca333 /llvm/lib/CodeGen/MachineCombiner.cpp | |
| parent | d1180f4abc267ed041744df2204b846f18f6d554 (diff) | |
| download | bcm5719-llvm-8b05278b4ebbce338fbd5604340a64dab6c8d415.tar.gz bcm5719-llvm-8b05278b4ebbce338fbd5604340a64dab6c8d415.zip | |
tests: Add test that has a single pointer both as scalar read and array base
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
Diffstat (limited to 'llvm/lib/CodeGen/MachineCombiner.cpp')
0 files changed, 0 insertions, 0 deletions
