This will help refactoring some of the tools to prepare for the explicit registration of
Dialects.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM if towards removing static registration
mlir/include/mlir/Support/MlirOptMain.h | ||
---|---|---|
29 | passPipeline as name for arg that is a CL pass pipeline parser, seems confusing. Could passes be passed in rather than parsed inside? (And so be a passed in pass pipeline). Else why not call it a parser? | |
mlir/lib/Support/MlirOptMain.cpp | ||
181 | Mmm, this almost feels like something that should always be displayed in help message rather than with separate option (like what targets are linked in effectively). Passes effectively are. Up to you. |
List dialects in --help
mlir/include/mlir/Support/MlirOptMain.h | ||
---|---|---|
29 | The naming is weird but PassPipelineCLParser is the object that contains the result of the parsing. I'm open to suggestion on how to change this, but right now I'm not changing this API, just documenting it ; so I'll leave it for a subsequent revision | |
mlir/lib/Support/MlirOptMain.cpp | ||
181 | Added the list in the output of --help I'll keep this for now as the --help is very long and one may just want the list and nothing else. We can remove later if needed. |
passPipeline as name for arg that is a CL pass pipeline parser, seems confusing. Could passes be passed in rather than parsed inside? (And so be a passed in pass pipeline). Else why not call it a parser?