| commit | 5e5bf20dd20abdbb96d6897f780fd72e4737bd59 | |
| author | Sven Verdoolaege <skimo@kotnet.org> | |
| Fri, 19 Apr 2013 08:08:11 +0000 (19 10:08 +0200) | ||
| committer | Sven Verdoolaege <skimo@kotnet.org> | |
| Fri, 19 Apr 2013 19:35:15 +0000 (19 21:35 +0200) | ||
| tree | badd8da64db59f898ec2dd3527ca210384c83420 | treesnapshot (tar.gz zip) |
| parent | 3a742b3c0be668c77a68c8c687d9106952bc6633 | commitdiff |
isl_ast_build_ast_from_schedule: also add stride guard in generic case
Any guard implied by the stride constraint in the AST build domain
needs to be enforced by the generated AST and may not necessarily
be implied by the strided loop itself.
We were already adding this guard to the graft in the degenerate case,
but not in the generic case.
The implied guard is usually already available in loop bounds constraints,
so it is not clear if this fixes any bug that can appear in practice,
However, this may just be a consequence of the internal representation of sets
and we should not depend too much on this internal representation.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
Any guard implied by the stride constraint in the AST build domain
needs to be enforced by the generated AST and may not necessarily
be implied by the strided loop itself.
We were already adding this guard to the graft in the degenerate case,
but not in the generic case.
The implied guard is usually already available in loop bounds constraints,
so it is not clear if this fixes any bug that can appear in practice,
However, this may just be a consequence of the internal representation of sets
and we should not depend too much on this internal representation.
Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
| isl_ast_codegen.c | diffblobblamehistory |