| commit | e20b79898c93694e492d1a5f2d20690ac3a36528 | |
| author | Sven Verdoolaege <skimo@kotnet.org> | |
| Thu, 30 Oct 2014 13:09:54 +0000 (30 14:09 +0100) | ||
| committer | Sven Verdoolaege <skimo@kotnet.org> | |
| Thu, 16 Apr 2015 07:00:35 +0000 (16 09:00 +0200) | ||
| tree | 3ccb8a17bc5c990f17ea8b8d57f3d5c455cb4d6c | treesnapshot (tar.gz zip) |
| parent | 4dc131f1b6d7c6ee7a4952d85221ac20b9f412d5 | commitdiff |
gpu: stop mapping array to shared memory if no consecutive elements are accessed
An access that never accesses consecutive elements cannot be coalesced,
at least not using the current scheme, so there is no point in mapping
the array to shared memory for the sole purpose of improving coalescing.
Check whether an access accesses consecutive memory elements and, if not,
consider the access as coalesced already so that the non-coalesced
property will not cause the array to be mapped to shared memory.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
An access that never accesses consecutive elements cannot be coalesced,
at least not using the current scheme, so there is no point in mapping
the array to shared memory for the sole purpose of improving coalescing.
Check whether an access accesses consecutive memory elements and, if not,
consider the access as coalesced already so that the non-coalesced
property will not cause the array to be mapped to shared memory.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
| gpu_group.c | diffblobblamehistory |