diff options
| author | Tobias Grosser <tobias@grosser.es> | 2016-07-14 10:22:25 +0000 |
|---|---|---|
| committer | Tobias Grosser <tobias@grosser.es> | 2016-07-14 10:22:25 +0000 |
| commit | f384594d5e4960635434a38bcfd495840eff9c7e (patch) | |
| tree | ad876a0cea64b0a3b83634190e44fde3858bc153 /lldb/packages/Python/lldbsuite/test/python_api/interpreter/main.c | |
| parent | e938517e379160d3033557af5c6fcf8a89a4910f (diff) | |
| download | bcm5719-llvm-f384594d5e4960635434a38bcfd495840eff9c7e.tar.gz bcm5719-llvm-f384594d5e4960635434a38bcfd495840eff9c7e.zip | |
GPGPU: compute new schedule from polly scop
To do so we copy the necessary information to compute an initial schedule from
polly::Scop to ppcg's scop. Most of the necessary information is directly
available and only needs to be passed on to ppcg, with the exception of 'tagged'
access relations, access relations that additionally carry information about
which memory access an access relation originates from.
We could possibly perform the construction of tagged accesses as part of
ScopInfo, but as this format is currently specific to ppcg we do not do this
yet, but keep this functionality local to our GPU code generation.
After the scop has been initialized, we compute data dependences and ask ppcg to
compute an initial schedule. Some of this functionality is already available in
polly::DependenceInfo and polly::ScheduleOptimizer, but to keep differences
to ppcg small we use ppcg's functionality here. We may later investiage if
a closer integration of these tools makes sense.
llvm-svn: 275390
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/interpreter/main.c')
0 files changed, 0 insertions, 0 deletions
