Fusilli <> tuner v1: Add IREE tuner integration via Python wrapper script#339
Fusilli <> tuner v1: Add IREE tuner integration via Python wrapper script#339bangtianliu wants to merge 1 commit into
Conversation
eb36257 to
73a7040
Compare
6cef352 to
53ddb1f
Compare
81509d0 to
09dee93
Compare
|
I think this is a useful next step but I am pretty confused why you'd want to integrate it at the fusilli core layer when all the direct consumers of this will be at the fusilli provider layer. That's the main user facing interface for fusilli (via hipdnn) and this fits there. @AaronStGeorge could you share what would be a good interface point and next steps to get this integrated properly? |
Thanks for the pointer, that link is helpful. You're right, the mistake on my end came from a lack of context about where fusilli is actually used. |
Adds `benchmarks/run_tuner.py`, a Python wrapper around `amdsharktuner.libtuner` that allows non-expert users to invoke the IREE tuner directly from Fusilli. The script runs the full tuning pipeline: generate MLIR via the benchmark driver, extract cached artifacts, generate/compile/benchmark tuning candidates, and output an optimized tuning spec. Supports single-command and multi-command (spec-chaining) workflows. Signed-off-by: Bangtian Liu <liubangtian@gmail.com>
09dee93 to
0d241e3
Compare
This PR adds
benchmarks/run_tuner.py, a Python wrapper aroundamdsharktuner.libtunerthat lets non-expert users invoke the IREE tuner directly from Fusilli.Issue: #255
Assisted-by: Claude Code