| commit | b2eda39531cbe09b3fa8cc05cf42825519ceb2f5 | [log] [tgz] |
|---|---|---|
| author | bjacob <benoitjacob@google.com> | Mon Nov 28 14:46:57 2022 -0500 |
| committer | GitHub <noreply@github.com> | Mon Nov 28 14:46:57 2022 -0500 |
| tree | 15fe3d5254aede7066b9abf9e5eb867bccd7edd6 | |
| parent | 79d9a3c5f62f65a2e537ba9ad381c665488c36a1 [diff] |
Consistently query `ExecutableTargetAttr` (#11291) #11057 added a `IREE::HAL::ExecutableTargetAttr::lookup` function which should be the preferred way to get a `ExecutableTargetAttr`, since it honors the overrides made possible by that PR. It's also neatly shrinking code at call sites, and better conveys intent: before, we were querying a `ExecutableVariantOp` only to get at the `ExecutableTargetAttr`, now we query directly the latter. The Utils are updated to all take a `ExecutableTargetAttr`, and since they were already implementing logic to handle optionally present fields, this further simplifies logic at call sites. Some Utils implementation functions, which were internal, are now exposed in `Utils.h`. Particularly `getConfigStringAttr`. There seemed to be no point having various place in the code reimplement that boilerplate themselves (with opportunities to mishandle optionals). A new `getConfigIntegerAttr` is added. This is preparation for determining tile sizes based on target info in `MaterializeEncoding`, which following #11290 we will be able to do based on the `ExecutableTargetAttr` which we query there. It would be inconvenient, at least for testing purposes, to have to deal only with `ExecutableVariantOp` there, so the new `MaterializeEncoding` code in #11290 is using `IREE::HAL::ExecutableTargetAttr::lookup` and needs to access helpers taking a `ExecutableTargetAttr`, which was the original motivation for the `Utils.*` changes here.
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.