Skip to content

Commit

Permalink
[mlir] Fix usages of run-reproducer.
Browse files Browse the repository at this point in the history
There is no need to specify `run-reproducer` explicitly anymore.

Differential Revision: https://reviews.llvm.org/D129010
  • Loading branch information
rdzhabarov committed Jul 1, 2022
1 parent 258c3ae commit f59c279
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 5 deletions.
6 changes: 3 additions & 3 deletions mlir/docs/PassManagement.md
Expand Up @@ -1284,9 +1284,9 @@ module {
#-}
```
The configuration dumped can be passed to `mlir-opt` by specifying
`-run-reproducer` flag. This will result in parsing the configuration of the reproducer
and adjusting the necessary opt state, e.g. configuring the pass manager, context, etc.
The configuration dumped can be passed to `mlir-opt`. This will result in
parsing the configuration of the reproducer and adjusting the necessary opt
state, e.g. configuring the pass manager, context, etc.
Beyond specifying a filename, one can also register a `ReproducerStreamFactory`
function that would be invoked in the case of a crash and the reproducer written
Expand Down
2 changes: 0 additions & 2 deletions mlir/utils/jupyter/mlir_opt_kernel/kernel.py
Expand Up @@ -128,8 +128,6 @@ def run(code):
'-o',
'-'
]
if code.startswith('// configuration:'):
command.append('--run-reproducer')
# Simple handling of repeating last line.
if code.endswith('\n_'):
if not self._:
Expand Down

0 comments on commit f59c279

Please sign in to comment.