Currently -pass-pipeline can be specified multiple times and mixed
with the individual -pass-name options. Removing this feature will
allow for including the pipeline anchor as part of the option
argument (see D134900).
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
address comments
mlir/include/mlir/Pass/PassRegistry.h | ||
---|---|---|
259 | PassPipelineCLParserImpl is used by PassNameCLParser as well, so moving the option into there causes it to be registered twice. | |
mlir/lib/Pass/PassRegistry.cpp | ||
923–924 | fixed, but since the messages from parsePassPipeline don't have a consistent format some cases end up looking odd, e.g. $ mlir-opt -pass-pipeline='unbalanced(' MLIR Textual PassPipeline Parser:1:12: error: encountered unbalanced parentheses while parsing pipeline unbalanced( ^ becomes: $ mlir-opt -pass-pipeline='unbalanced(' <unknown>:0: error: MLIR Textual PassPipeline Parser:1:12: error: encountered unbalanced parentheses while parsing pipeline unbalanced( ^ (the <location>: error: part is being printed twice) |
@rriddle could you take another look at this? it's the last patch in the stack that needs review
LGTM. Apologies for the delay, I've been a little swamped lately.
mlir/lib/Pass/PassRegistry.cpp | ||
---|---|---|
923–924 | Hmmm, can you file an issue for that? It'd be good to have a nice experience here. |
mlir/lib/Pass/PassRegistry.cpp | ||
---|---|---|
923–924 |
Can you move this to the impl?