| commit | 1774f9a54cc67f27eadf03f3b17e19bf0e2b0208 | |
| author | Sven Verdoolaege <skimo@kotnet.org> | |
| Wed, 24 Jun 2015 08:57:04 +0000 (24 10:57 +0200) | ||
| committer | Sven Verdoolaege <skimo@kotnet.org> | |
| Sat, 4 Jul 2015 13:59:50 +0000 (4 15:59 +0200) | ||
| tree | 0cec685ede8e7bd8788f4b2048ba06ba185a6b9e | treesnapshot (tar.gz zip) |
| parent | d4b29e478c1eb250362c7e94b93d30be1035fbbf | commitdiff |
gpu_group.c: access_is_coalesced: handle zero-dimensional data
The function access_is_coalesced is only called when there is no reuse.
If the array is zero-dimensional, then this means it is accessed
exactly once. This is fairly unlikely, but it can happen if
PPCG gets confused about the amount of available parallelism.
Although in such cases, the produced code would be suboptimal,
we should at least produce some code instead of erroring out.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
The function access_is_coalesced is only called when there is no reuse.
If the array is zero-dimensional, then this means it is accessed
exactly once. This is fairly unlikely, but it can happen if
PPCG gets confused about the amount of available parallelism.
Although in such cases, the produced code would be suboptimal,
we should at least produce some code instead of erroring out.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
| gpu_group.c | diffblobblamehistory |