[Mlir-commits] [mlir] [mlir][transform] Overhaul `RegionBranchOpInterface` implementations. (PR #111408)
Matthias Springer
llvmlistbot at llvm.org
Thu Oct 10 04:58:11 PDT 2024
Ingo =?utf-8?q?Müller?= <ingomueller at google.com>
Message-ID:
In-Reply-To: <llvm.org/llvm/llvm-project/pull/111408 at github.com>
================
@@ -104,16 +104,8 @@ transform::AlternativesOp::getEntrySuccessorOperands(RegionBranchPoint point) {
void transform::AlternativesOp::getSuccessorRegions(
RegionBranchPoint point, SmallVectorImpl<RegionSuccessor> ®ions) {
- for (Region &alternative : llvm::drop_begin(
----------------
matthias-springer wrote:
I was wondering about this line:
```
regions.push_back(RegionSuccessor(&getRegion()));
```
A region is specified but no basic block arguments.
So I am trying to understand if this interface can be used to model branches between regions, without modeling any data flow via block arguments. (I think it is possible.)
https://github.com/llvm/llvm-project/pull/111408
More information about the Mlir-commits
mailing list