This adds a --no-implicit-module option, which disables the insertion
of a top-level builtin.module during parsing. Although other ops can
now be parsed as top-level, the actual reduction passes are still
restricted to builtin.module as it didn't seem straightforward to
update them.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/lib/Tools/mlir-reduce/MlirReduceMain.cpp | ||
---|---|---|
25 | bazel file missing, again |
mlir/lib/Tools/mlir-reduce/MlirReduceMain.cpp | ||
---|---|---|
25 | is it expected that all MLIR changes should update the bazel files as well? i was under the impression that the bazel files were maintained separately by bazel users. |
mlir/lib/Tools/mlir-reduce/MlirReduceMain.cpp | ||
---|---|---|
25 | No I don't think there is a general expectation for this. I think today I am the lucky bazel user that needs to keep this consistent ;-) |
mlir/lib/Tools/mlir-reduce/MlirReduceMain.cpp | ||
---|---|---|
25 | There is no requirement to update bazel, it's a best effort done only by bazel users. |