#sdy Add an event to the op priority schedule to propagate through all ops after element-wise ops, but **only** through non-passthrough factors. #384
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.
#sdy Add an event to the op priority schedule to propagate through all ops after element-wise ops, but only through non-passthrough factors.
In the test case added
pass_through_factor_higher_priority_than_reduction_factor
, before we'd shard%arg0
to[{?}, {"a", ?}]
due to sideways propagation on the reduction factor. But now we halt that while we propagate through the non-contracting dim backwards from the result to get[{"a", ?}, {?}]
.