activeDomainPoints: do not take into account mapping filters

In a subsequent commit, mapping filters will no longer be considered
to be filters.  Change activeDomainPoints first to isolate the effect
of this change on activeDomainPoints.
There are many calls to activeDomainPoints, so it's not trivial
to verify that not including mapping filters is always the right
thing to do.  However, the included mapping filters are usually
seen as a nuisance and if they are really needed in some cases
then it's better to take them into account explicitly
in those particular cases.

Author: Sven Verdoolaege

tc/core/polyhedral/schedule_transforms.cc

@@ -105,8 +105,8 @@ namespace {
 /*
  * If "node" is any filter, then intersect "domain" with that filter.
  */
-isl::union_set applyAnyFilter(isl::union_set domain, const ScheduleTree* node) {
-  if (auto filterElem = node->elemAsBase<ScheduleTreeElemFilter>()) {
+isl::union_set applyFilter(isl::union_set domain, const ScheduleTree* node) {
+  if (auto filterElem = node->elemAs<ScheduleTreeElemFilter>()) {
     return domain.intersect(filterElem->filter_);
   }
   return domain;
@@ -155,7 +155,7 @@ isl::union_set collectDomain(
 isl::union_set activeDomainPointsHelper(
     const ScheduleTree* root,
     const vector<const ScheduleTree*>& nodes) {
-  return collectDomain(root, nodes, &applyAnyFilter);
+  return collectDomain(root, nodes, &applyFilter);
 }
 
 } // namespace