When reading parameters from a JSON file parameters with identical names
may be related to different isl_ids, which then causes isl to treat them
as differnet objects. This does not cause issues at the moment, but has
shown problematic in subsequent schedule tree changes.
This commit will be tested by the following changes.
llvm-svn: 235588
// that stores the reference to the ScopStmt this schedule belongs to.
m = isl_map_set_tuple_id(m, isl_dim_in,
isl_space_get_tuple_id(Space, isl_dim_set));
+ for (unsigned i = 0; i < isl_space_dim(Space, isl_dim_param); i++) {
+ isl_id *id = isl_space_get_dim_id(Space, isl_dim_param, i);
+ m = isl_map_set_dim_id(m, isl_dim_param, i, id);
+ }
isl_space_free(Space);
NewSchedule[*SI] = m;
index++;