| commit | 13865c6789bbc047bf2541b32f646230c92570d5 | |
| author | Sven Verdoolaege <skimo@kotnet.org> | |
| Thu, 11 Apr 2013 15:36:38 +0000 (11 17:36 +0200) | ||
| committer | Sven Verdoolaege <skimo@kotnet.org> | |
| Mon, 22 Apr 2013 07:38:19 +0000 (22 09:38 +0200) | ||
| tree | fc2ab51f80ae2c5961e7f14aec576c96ad83dc85 | treesnapshot (tar.gz zip) |
| parent | f4e69899128bc20f66eb3fe12ffbc73a9c29a537 | commitdiff |
isl_ast_codegen.c: create_node_scaled: reflect current domain slice in schedule
If we detect that a given schedule dimension has a fixed (possibly
parametric) value, then this value is recorded in the build and
the schedule dimension is eliminated. This elimination process may
drop constraints on the part of the domain that we are currently considering,
which may cause all sorts of problems. In particular, we may fail
to discover at the end of the AST generation that the original schedule
was single valued and insert spurious loops.
Plug in the value we found instead of simply eliminating the schedule
dimension.
Reported-by: Tobias Grosser <tobias@grosser.es>
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
If we detect that a given schedule dimension has a fixed (possibly
parametric) value, then this value is recorded in the build and
the schedule dimension is eliminated. This elimination process may
drop constraints on the part of the domain that we are currently considering,
which may cause all sorts of problems. In particular, we may fail
to discover at the end of the AST generation that the original schedule
was single valued and insert spurious loops.
Plug in the value we found instead of simply eliminating the schedule
dimension.
Reported-by: Tobias Grosser <tobias@grosser.es>
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>