To my understanding this functionality is not present in MLIR yet. But other projects have implemented a similar mechanism to supply/parse a second MLIR file based on an optional path.
Check this reply to a similar question:
To my understanding this functionality is not present in MLIR yet. But other projects have implemented a similar mechanism to supply/parse a second MLIR file based on an optional path.
Check this reply to a similar question: