| commit | 6976c9dac117d600c5e5c1406e518c6b789f1fed | |
| author | Sven Verdoolaege <skimo@kotnet.org> | |
| Wed, 25 Mar 2015 11:39:26 +0000 (25 12:39 +0100) | ||
| committer | Sven Verdoolaege <skimo@kotnet.org> | |
| Fri, 27 Mar 2015 11:56:05 +0000 (27 12:56 +0100) | ||
| tree | d2a9e945da16ff331cd9799488fbd7704e5a1159 | treesnapshot (tar.gz zip) |
| parent | a5e4a8c8aa431c61f2e7bdaa3a99413b9dc06048 | commitdiff |
isl_schedule_constraints_compute_schedule: handle conditional validity after band
Conditional validity constraints are currently only handled during
the construction of a band. That is, only within the construction
of a band does the scheduler ensure that there are no non-local
conditions that are adjacent to violated conditional validity constraints.
However, a band may still result in non-local conditions and then
the conditional validity constraints need to be enforced by inner bands.
This issue does not show up very frequently because by the time
the conditions become non-local, the adjacent conditional validity
constraints have usually already been removed from the dependence graph,
but it does still happen.
A test case will be added on the master branch.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
Conditional validity constraints are currently only handled during
the construction of a band. That is, only within the construction
of a band does the scheduler ensure that there are no non-local
conditions that are adjacent to violated conditional validity constraints.
However, a band may still result in non-local conditions and then
the conditional validity constraints need to be enforced by inner bands.
This issue does not show up very frequently because by the time
the conditions become non-local, the adjacent conditional validity
constraints have usually already been removed from the dependence graph,
but it does still happen.
A test case will be added on the master branch.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
| isl_scheduler.c | diffblobblamehistory |