[Mlir-commits] [mlir] [MLIR][Python] remove `liveOperations` (PR #155114)
John Demme
llvmlistbot at llvm.org
Tue Sep 23 21:05:16 PDT 2025
teqdruid wrote:
> and be accessible/reachable by you at the point at which you return from the call to the pass manager.
Yes, this is the trick. I don't have a centralized, fool-proof way of tracking _all_ of the operations which get created. `liveOperations` gave me that.
Given my statement regarding debug-ability above, is there any interest in adding this to the MLIR Python bindings themselves? Or am I the only one who has scars from this issue?
We'd just have to track the set of all `Operation`s which have been created (either constructed from Python or by the bindings while crawling the IR) and haven't been deconstructed yet. Seems like that would be easy in the C++ bindings, wouldn't take up more space than `liveOperations`, and invalidations would be the responsibility of the user.
https://github.com/llvm/llvm-project/pull/155114
More information about the Mlir-commits
mailing list