You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -176,6 +176,9 @@ For detailed instructions on how to debug Triton's frontend, please refer to thi
176
176
kernels. Use `MLIR_ENABLE_DUMP=kernelName` to dump for a specific kernel only.
177
177
- Triton cache can interfere with the dump. In cases where `MLIR_ENABLE_DUMP=1` does not work, try cleaning your triton cache: `rm -r ~/.triton/cache/*`
178
178
-`LLVM_IR_ENABLE_DUMP=1` dumps the IR before every pass run over the LLVM IR.
179
+
-`TRITON_REPRODUCER_PATH=<reproducer_path>` will generate an MLIR reproducer file
180
+
at `<reproducer_path>` before each MLIR compiler stage. If any of the stages fail,
181
+
`<reproducer_path>` will be a local MLIR reproducer captured right before the failing pass.
179
182
-`TRITON_INTERPRET=1` uses the Triton interpreter instead of running on the
180
183
GPU. You can insert Python breakpoints in your kernel code!
181
184
-`TRITON_ENABLE_LLVM_DEBUG=1` passes `-debug` to LLVM, printing a lot of
0 commit comments