Support nested SDFGs in distributed lowering #123
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows us to support reductions with their intialization states.
The idea is that nested SDFG are required to be schedule such that there
is no communication within them. The user passes the schedules for each
map, and the implied communication constraints are then checked for
consistency.
Keeping communication out of the Nested SDFGs means that there is no
communication between things like reduction buffer initialization, and
also means that all global communication is kept top-level, where it is
easier to optimize