This is possible by adding two new ControlFlowInterface additions:
- A new interface, RegionBranchOpInterface
This interface allows for region holding operations to describe how control flows between regions. This interface initially contains two methods:
- getSuccessorEntryOperands
Returns the operands of this operation used as the entry arguments when entering the region at index, which was specified as a successor by getSuccessorRegions. when entering. These operands should correspond 1-1 with the successor inputs specified in getSuccessorRegions, and may be a subset of the entry arguments for that region.
- getSuccessorRegions
Returns the viable successors of a region, or the possible successor when branching from the parent op. This allows for describing which regions may be executed when entering an operation, and which regions are executed after having executed another region of the parent op. For example, a structured loop operation may always enter into the loop body region. The loop body region may branch back to itself, or exit to the operation.
- A trait, ReturnLike
This trait signals that a terminator exits a region and forwards all of its operands as "exiting" values.
These additions allow for performing more general dataflow analysis in the presence of region holding operations.
Depends On D78397
I think this should be called getSuccessorRegionEntryOperands or getSuccRegionEntryOperands.