-
Notifications
You must be signed in to change notification settings - Fork 15.4k
[MLIR] Fix pipelineInitializationKey never being correctly updated #150948
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
[MLIR] Fix pipelineInitializationKey never being correctly updated #150948
Conversation
|
@llvm/pr-subscribers-mlir-core Author: Will Froom (WillFroom) ChangesPrior to this change Full diff: https://github.com/llvm/llvm-project/pull/150948.diff 1 Files Affected:
diff --git a/mlir/lib/Pass/Pass.cpp b/mlir/lib/Pass/Pass.cpp
index 0db9808b722a7..7094c8e279f2d 100644
--- a/mlir/lib/Pass/Pass.cpp
+++ b/mlir/lib/Pass/Pass.cpp
@@ -901,7 +901,7 @@ LogicalResult PassManager::run(Operation *op) {
if (failed(initialize(context, impl->initializationGeneration + 1)))
return failure();
initializationKey = newInitKey;
- pipelineKey = pipelineInitializationKey;
+ pipelineInitializationKey = pipelineKey;
}
// Construct a top level analysis manager for the pipeline.
|
|
@llvm/pr-subscribers-mlir Author: Will Froom (WillFroom) ChangesPrior to this change Full diff: https://github.com/llvm/llvm-project/pull/150948.diff 1 Files Affected:
diff --git a/mlir/lib/Pass/Pass.cpp b/mlir/lib/Pass/Pass.cpp
index 0db9808b722a7..7094c8e279f2d 100644
--- a/mlir/lib/Pass/Pass.cpp
+++ b/mlir/lib/Pass/Pass.cpp
@@ -901,7 +901,7 @@ LogicalResult PassManager::run(Operation *op) {
if (failed(initialize(context, impl->initializationGeneration + 1)))
return failure();
initializationKey = newInitKey;
- pipelineKey = pipelineInitializationKey;
+ pipelineInitializationKey = pipelineKey;
}
// Construct a top level analysis manager for the pipeline.
|
b7fa80f to
4a61668
Compare
|
Thanks for the fix! |
I can, could you point me towards any existing test that I could add to? |
in It can be adapted to running the pm multiple times and check the |
|
Thanks for the pointer @jackalcooper! |
Prior to this change
pipelineInitializationKeywould never be updated soinitializewould always be called even if the pipeline didn't change