diff options
| author | Tobias Grosser <tobias@grosser.es> | 2015-04-21 11:37:25 +0000 |
|---|---|---|
| committer | Tobias Grosser <tobias@grosser.es> | 2015-04-21 11:37:25 +0000 |
| commit | 54839311177600cda6fa8f4daedc5e7524bfb638 (patch) | |
| tree | 356c4774bf80dbe0d408214b2a1eaff15ad9ae96 /llvm/unittests/ProfileData/CoverageMappingTest.cpp | |
| parent | 8e086cedfa36cd3badb6cfcb1b19811dcdc4c3b3 (diff) | |
| download | bcm5719-llvm-54839311177600cda6fa8f4daedc5e7524bfb638.tar.gz bcm5719-llvm-54839311177600cda6fa8f4daedc5e7524bfb638.zip | |
Rename 'scattering' to 'schedule'
In Polly we used both the term 'scattering' and the term 'schedule' to describe
the execution order of a statement without actually distinguishing between them.
We now uniformly use the term 'schedule' for the execution order. This
corresponds to the terminology of isl.
History: CLooG introduced the term scattering as the generated code can be used
as a sequential execution order (schedule) or as a parallel dimension
enumerating different threads of execution (placement). In Polly and/or isl the
term placement was never used, but we uniformly refer to an execution order as a
schedule and only later introduce parallelism. When doing so we do not talk
about about specific placement dimensions.
llvm-svn: 235380
Diffstat (limited to 'llvm/unittests/ProfileData/CoverageMappingTest.cpp')
0 files changed, 0 insertions, 0 deletions
