| commit | a3a64d2646e6f8ef95f514fdbdad7bc34f1d51c1 | [log] [tgz] |
|---|---|---|
| author | Ben Vanik <ben.vanik@gmail.com> | Wed Oct 25 10:16:57 2023 -0700 |
| committer | GitHub <noreply@github.com> | Wed Oct 25 10:16:57 2023 -0700 |
| tree | ed8ff441568533010d3501ea65e5f07ab236a54e | |
| parent | 466e812764beb3eeafebba5e5a45324cd40b5341 [diff] |
Adding selection condition to hal.executable.variant. (#15284) This allows for variants to declare host logic that determines whether the variant should be selected for loading. When multiple variants are available their declared conditions will be evaluated in op order along with the existing executable format match. Unfortunately the MLIR SymbolTable trait disallows multiple regions on any op holding it so a new `hal.executable.condition` region op was added that may be optionally present on any `hal.executable.variant`. Ideally we clean this up and make it an optional region but that'll need relaxing of upstream assertions like https://sourcegraph.com/github.com/llvm/llvm-project/-/blob/mlir/lib/IR/SymbolTable.cpp?L122-123 (ideally either treating region 0 as the symbol table on ops or having an interface override for selecting the region ala `getCallableRegion` such as `getSymbolTableRegion`). This removes the `hal.device.switch` op in favor of `scf.index_switch`. When we start running const expr hoisting during the HAL pipeline this should allow variant selection to be completely hoisted to initialization time (or at least memoized per device). There's decent low-hanging future work on optimizing the ranking/selection and improving `scf.index_switch` hoisting/canonicalization to make things better.
IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.
See our website for project details, user guides, and instructions on building from source.
IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!
See our website for more information.
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.