feat: allow fine-grained control on verbosity settings

This commit is contained in:
Umut
2022-12-07 11:06:08 +01:00
parent 5a8fe7cdda
commit a25ba9b7f4
5 changed files with 46 additions and 14 deletions

View File

@@ -52,17 +52,20 @@ Additional kwarg to `compile` function have higher precedence. So if you set an
## Options
* **show\_graph**: bool = False
* **show\_graph**: Optional[bool] = None
* Whether to print computation graph during compilation.
`True` means always to print, `False` means always to not print, `None` means print depending on verbose configuration below.
* **show\_mlir**: bool = False
* **show\_mlir**: Optional[bool] = None
* Whether to print MLIR during compilation.
`True` means always to print, `False` means always to not print, `None` means print depending on verbose configuration below.
* **show\_optimizer**: bool = False
* **show\_optimizer**: Optional[bool] = None
* Whether to print optimizer output during compilation.
`True` means always to print, `False` means always to not print, `None` means print depending on verbose configuration below.
* **verbose**: bool = False
* Whether to print computation graph and MLIR during compilation.
* Whether to print details related to compilation.
* **dump\_artifacts\_on\_unexpected\_failures**: bool = True
* Whether to export debugging artifacts automatically on compilation failures.