When tooling out there produces a reproducer that is archived, the first thing
a user is likely to expect is to process this as they do with any MLIR file.
However https://reviews.llvm.org/D126447 changed the behavior of mlir-opt to
eliminate the --run-reproducer option and instead automatically run it when
present in the input file. This creates a discrepancy in how mlir-opt behaves
when fed with an input file, and is surprising for users.
The explicit passing of --run-reproducer to express user-intent seems more
in line with what is expected from mlir-opt.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/include/mlir/Tools/mlir-opt/MlirOptMain.h | ||
---|---|---|
119 | docstring needs updating | |
mlir/lib/Tools/mlir-opt/MlirOptMain.cpp | ||
261–263 | Can you guard the reproOptions.attachResourceParser(parseConfig) line instead/as well, right now the resource would be "consumed" even if unused, and won't appear in the output IR. |
docstring needs updating