[Mlir-commits] [mlir] [mlir][pass] Allow reregistration of pass with same typeids (PR #72067)
Mehdi Amini
llvmlistbot at llvm.org
Mon Nov 13 08:33:46 PST 2023
================
@@ -181,4 +182,48 @@ TEST(PassManagerTest, PassInitialization) {
EXPECT_TRUE(succeeded(pm.run(module.get())));
}
+struct ReRegisterPass
+ : public PassWrapper<ReRegisterPass, OperationPass<ModuleOp>> {
+ MLIR_DEFINE_EXPLICIT_INTERNAL_INLINE_TYPE_ID(ReRegisterPass)
+
+ ReRegisterPass(std::string annotation) : annotation(annotation) {}
+
+ std::string annotation;
+
+ void runOnOperation() override {
+ ModuleOp op = this->getOperation();
+ Builder builder(op);
+ op->walk([this, &builder](Operation *op) {
+ op->setAttr(annotation, builder.getUnitAttr());
+ });
+ }
+};
+
+TEST(PassManagerTest, PassReRegistration) {
+ MLIRContext context;
+ context.allowUnregisteredDialects();
+
+ std::string moduleStr = R"mlir(
+ module {
+ "custom.op1"() : () -> ()
+ "custom.op2"() : () -> ()
+ }
+ )mlir";
+
+ OwningOpRef<ModuleOp> module =
+ parseSourceString<ModuleOp>(moduleStr, &context);
+
+ // Instantiate and run pass in first configuration.
+ auto pm = PassManager::on<ModuleOp>(&context);
+ pm.addPass(std::make_unique<ReRegisterPass>("custom.first"));
+ EXPECT_TRUE(succeeded(pm.run(module.get())));
+ module->walk([](Operation *op) { EXPECT_TRUE(op->hasAttr("custom.first")); });
+
+ // Adding a "reconfiguration" of the pass, i.e., with a different annotation.
+ pm.addPass(std::make_unique<ReRegisterPass>("custom.second"));
----------------
joker-eph wrote:
I'm still not sure what's the problem or how you're change here is solving it in a principled way?
One registration over-writing silently the previous one does not seem better to me than ignoring the second one. Actually I'd say it is worse: it would make your example work, so someone may think it is fine, when it turns out they over-wrote something. Better have it just "not work".
The problem is that writing such a pass that isn't "hermetic" is not desirable. But I don't see how we can protect people against themselves? That is: it is C++ and folks have access to every low-level aspects of the language.
https://github.com/llvm/llvm-project/pull/72067
More information about the Mlir-commits
mailing list