// Converts MLIR lit test files to `bazel run` commands. Use when you need to convert a failing MLIR lit test target (containing RUN lines) to a shell command whose flags can be modified for further analysis and debugging.
Converts end-to-end (e2e) test targets or paths to `bazel run` commands for `heir-opt`. Use when you need to convert an e2e test target (where flags are defined in the BUILD file) to a shell command whose flags can be modified for further analysis and debugging.
Describes a decision tree of steps and skills to utilize when, starting from a test failure or the failure of `bazel run` command using heir-opt, you would like to produce a reproducing input IR that fails on a particular compiler pass.
Augments a `bazel run` CLI command for `heir-opt` with additional flags that dump the IR before each compiler pass, allowing the agent to inspect intermediate IR during compilation, identify a particular pass at which the pipeline fails, or extract the corresponding IR input to a particular pass for further debugging.
| name | lit-to-bazel |
| description | Converts MLIR lit test files to `bazel run` commands. Use when you need to convert a failing MLIR lit test target (containing RUN lines) to a shell command whose flags can be modified for further analysis and debugging. |
This skill guides the agent in using the lit_to_bazel tool to convert MLIR
test files to executable commands.
To convert a lit test file to a bazel run command, use the following command
recipes:
bazel run //third_party/heir/scripts:lit_to_bazel -- {test_file_path}
Replace {test_file_path} with the absolute path to the test file. The absolute
path is necessary because the bazel run command runs relative to its runfiles
directory, and so a relative path will not be relative to the VCS root of the
project.
%s in RUN lines with the absolute path
of the test file to ensure it works in the sandbox.lit_to_bazel tool.Copy this checklist and track progress:
- [ ] Step 1: Identify the test file to convert.
- [ ] Step 2: Run the `lit_to_bazel` tool on the file.
- [ ] Step 3: Inspect the generated command or run it.
- [ ] Step 4: Verify execution results.