| commit | 0948bc8939f8ef1b320447a65eea942fe1f61f70 | [log] [tgz] |
|---|---|---|
| author | Geoffrey Martin-Noble <gcmn@google.com> | Wed Mar 15 17:27:34 2023 -0700 |
| committer | GitHub <noreply@github.com> | Thu Mar 16 00:27:34 2023 +0000 |
| tree | 4e6a71fcd04d08df71f601d6e0dade51c2085106 | |
| parent | 7497689acb7125046625bc78dfb43dc7da9eff38 [diff] |
Be consistent about the use of IREE Bazel macros (#12645) We have some wrapper macros for various rules, mostly to add includes, but usage was not consistent. This still worked because includes are inherited transitively, but it only worked by accident basically. Classifying things this way is also helpful for differentiating compiler and runtime in bazel query and such (don't need to analyze the whole dep tree). It could also provide hook points to guard against cross-component dependencies.
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.