-
Notifications
You must be signed in to change notification settings - Fork 14.4k
[MLIR][Interfaces] Remove negative branch weight verifier #148234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[MLIR][Interfaces] Remove negative branch weight verifier #148234
Conversation
This commit removes the verifier that checked if branch weights are negative. This check was too strict because weights are interpreted as unsigned integers. This showed up when running the verifier on LLVM dialect modules that were imported from LLVM IR.
@llvm/pr-subscribers-mlir @llvm/pr-subscribers-mlir-cf Author: Christian Ulmann (Dinistro) ChangesThis commit removes the verifier that checked if branch weights are negative. This check was too strict because weights are interpreted as unsigned integers. This showed up when running the verifier on LLVM dialect modules that were imported from LLVM IR. Full diff: https://github.com/llvm/llvm-project/pull/148234.diff 3 Files Affected:
diff --git a/mlir/include/mlir/Interfaces/ControlFlowInterfaces.td b/mlir/include/mlir/Interfaces/ControlFlowInterfaces.td
index 46ab0b9ebbc6b..b8d08cc553caa 100644
--- a/mlir/include/mlir/Interfaces/ControlFlowInterfaces.td
+++ b/mlir/include/mlir/Interfaces/ControlFlowInterfaces.td
@@ -384,13 +384,15 @@ def WeightedBranchOpInterface : OpInterface<"WeightedBranchOpInterface"> {
This interface provides weight information for branching terminator
operations, i.e. terminator operations with successors.
- This interface provides methods for getting/setting integer non-negative
- weight of each branch. The probability of executing a branch
- is computed as the ratio between the branch's weight and the total
- sum of the weights (which cannot be zero).
- The weights are optional. If they are provided, then their number
+ This interface provides methods for getting/setting integer weights of each
+ branch. The probability of executing a branch is computed as the ratio
+ between the branch's weight and the total sum of the weights (which cannot
+ be zero). The weights are optional. If they are provided, then their number
must match the number of successors of the operation.
+ Note that the branch weight use an i32 representation but they are to be
+ interpreted as unsigned integers.
+
The default implementations of the methods expect the operation
to have an attribute of type DenseI32ArrayAttr named branch_weights.
}];
@@ -440,19 +442,21 @@ def WeightedRegionBranchOpInterface
This interface provides weight information for region operations
that exhibit branching behavior between held regions.
- This interface provides methods for getting/setting integer non-negative
- weight of each branch. The probability of executing a region is computed
- as the ratio between the region branch's weight and the total sum
- of the weights (which cannot be zero).
- The weights are optional. If they are provided, then their number
- must match the number of regions held by the operation
- (including empty regions).
+ This interface provides methods for getting/setting integer weights of each
+ branch. The probability of executing a region is computed as the ratio
+ between the region branch's weight and the total sum of the weights (which
+ cannot be zero). The weights are optional. If they are provided, then their
+ number must match the number of regions held by the operation (including
+ empty regions).
The weights specify the probability of branching to a particular
region when first executing the operation.
For example, for loop-like operations with a single region
the weight specifies the probability of entering the loop.
+ Note that the branch weight use an i32 representation but they are to be
+ interpreted as unsigned integers.
+
The default implementations of the methods expect the operation
to have an attribute of type DenseI32ArrayAttr named branch_weights.
}];
diff --git a/mlir/lib/Interfaces/ControlFlowInterfaces.cpp b/mlir/lib/Interfaces/ControlFlowInterfaces.cpp
index 3a63db35eec0f..e87bb461b0329 100644
--- a/mlir/lib/Interfaces/ControlFlowInterfaces.cpp
+++ b/mlir/lib/Interfaces/ControlFlowInterfaces.cpp
@@ -99,10 +99,6 @@ static LogicalResult verifyWeights(Operation *op,
<< ": " << weights.size() << " vs "
<< expectedWeightsNum;
- for (auto [index, weight] : llvm::enumerate(weights))
- if (weight < 0)
- return op->emitError() << "weight #" << index << " must be non-negative";
-
if (llvm::all_of(weights, [](int32_t value) { return value == 0; }))
return op->emitError() << "branch weights cannot all be zero";
diff --git a/mlir/test/Dialect/ControlFlow/invalid.mlir b/mlir/test/Dialect/ControlFlow/invalid.mlir
index 1b8de22a9ff9f..0a71c62ec31af 100644
--- a/mlir/test/Dialect/ControlFlow/invalid.mlir
+++ b/mlir/test/Dialect/ControlFlow/invalid.mlir
@@ -82,18 +82,6 @@ func.func @wrong_weights_number(%cond: i1) {
// -----
-// CHECK-LABEL: func @negative_weight
-func.func @wrong_total_weight(%cond: i1) {
- // expected-error@+1 {{weight #0 must be non-negative}}
- cf.cond_br %cond weights([-1, 101]), ^bb1, ^bb2
- ^bb1:
- return
- ^bb2:
- return
-}
-
-// -----
-
// CHECK-LABEL: func @zero_weights
func.func @wrong_total_weight(%cond: i1) {
// expected-error@+1 {{branch weights cannot all be zero}}
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix!
LGTM but let's give @vzakhari a chance to review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the fix!
This commit removes the verifier that checked if branch weights are negative. This check was too strict because weights are interpreted as unsigned integers.
This showed up when running the verifier on LLVM dialect modules that were imported from LLVM IR.