hanchenye-llvm-project/polly/test/ScopInfo/NonAffine
Tobias Grosser b3a85884f7 Do not use wrapping ranges to bound non-affine accesses
When deriving the range of valid values of a scalar evolution expression might
be a range [12, 8), where the upper bound is smaller than the lower bound and
where the range is expected to possibly wrap around. We theoretically could
model such a range as a union of two non-wrapping ranges, but do not do this
as of yet. Instead, we just do not derive any bounds. Before this change,
we could have obtained bounds where the maximal possible value is strictly
smaller than the minimal possible value, which is incorrect and also caused
assertions during scop modeling.

llvm-svn: 294891
2017-02-12 08:11:12 +00:00
..
div_backedge.ll
div_domain.ll
invariant_loads_dependent_in_non_affine_region.ll
modulo_backedge.ll
modulo_domain.ll
non-affine-loop-condition-dependent-access_1.ll Do not use wrapping ranges to bound non-affine accesses 2017-02-12 08:11:12 +00:00
non-affine-loop-condition-dependent-access_2.ll
non-affine-loop-condition-dependent-access_3.ll Update tests to more precise analysis results in LLVM core 2017-01-11 22:53:34 +00:00
non_affine_access_with_range_2.ll
non_affine_but_sdiv.ll
non_affine_but_srem.ll
non_affine_conditional_nested.ll
non_affine_conditional_surrounding_affine_loop.ll
non_affine_conditional_surrounding_non_affine_loop.ll
non_affine_float_compare.ll
non_affine_loop_condition.ll
non_affine_loop_used_later.ll Do not use wrapping ranges to bound non-affine accesses 2017-02-12 08:11:12 +00:00
non_affine_parametric_loop.ll Do not use wrapping ranges to bound non-affine accesses 2017-02-12 08:11:12 +00:00
non_affine_region_guaranteed_non-entry.ll
whole-scop-non-affine-subregion-in-loop.ll