[Relax][Bugfix] Apply FuseOps to nested DataflowBlock #17022
Closed
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.
While it is ill-formed for control-flow to occur within a
DataflowBlock
, it is legal for aDataflowBlock
to be contained within a control-flow. Prior to this commit, theFuseOps
andFuseOpsByPattern
transforms erroneously skippedDataflowBlock
instances that were contained within arelax::If
node.This commit updates
FuseOps
to apply operator fusion to any dataflow block, regardless of whether it is found at the top level of a a Relax function.