Google Git
Sign in
opensecura / 3p / openxla / iree / d8bf4acf4b7d4b72362972332debdcfce1c4682c
commitd8bf4acf4b7d4b72362972332debdcfce1c4682c[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Wed Jul 24 12:27:38 2024 -0700
committerGitHub <noreply@github.com>Wed Jul 24 19:27:38 2024 +0000
treef135738d8976871a1b53baa66956c50242f41e85
parent10877f61c2e73d578bb889012b84bbd1edf15ed0 [diff]
Add `iree-c-embed-data` and `iree-flatcc-cli` to release packages. (#18001)

Progress on https://github.com/iree-org/iree/issues/16203.

First, this renames `generate_embed_data` to `iree-c-embed-data`. The
name here dates back to having a single implementation shared across
multiple projects using Bazel (and Google's internal Blaze). There isn't
much code in the tool, but we've been using it for long enough to give
it a name matching our other tools IMO.

Next, this includes `iree-c-embed-data` and `iree-flatcc-cli` in the
`iree-runtime` Python package (https://pypi.org/project/iree-runtime/).
Both of these host tools are required for building large parts of the
runtime (embed data for builtins and bitcode, flatcc for schemas), so
including them in packages will allow users (and pkgci workflows) to get
them without needing to build from source.
33 files changed
tree: f135738d8976871a1b53baa66956c50242f41e85
  1. .github/
  2. build_tools/
  3. compiler/
  4. docs/
  5. experimental/
  6. integrations/
  7. lib/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazel_to_cmake.cfg.py
  15. .bazelignore
  16. .bazelrc
  17. .bazelversion
  18. .clang-format
  19. .dockerignore
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .pre-commit-config.yaml
  25. .yamllint.yml
  26. AUTHORS
  27. BUILD.bazel
  28. CITATION.cff
  29. CMakeLists.txt
  30. configure_bazel.py
  31. CONTRIBUTING.md
  32. LICENSE
  33. MAINTAINERS.md
  34. README.md
  35. RELEASING.md
  36. WORKSPACE
README.md

IREE: Intermediate Representation Execution Environment

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.

CI Status IREE Discord Status

Project Status

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!

Communication Channels

Related Project Channels

  • MLIR topic within LLVM Discourse: IREE is enabled by and heavily relies on MLIR. IREE sometimes is referred to in certain MLIR discussions. Useful if you are also interested in MLIR evolution.

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

Community meeting recordings: IREE YouTube channel

  • 2021-06-09: IREE Runtime Design Tech Talk (recording and slides)
  • 2020-08-20: IREE CodeGen: MLIR Open Design Meeting Presentation (recording and slides)
  • 2020-03-18: Interactive HAL IR Walkthrough (recording)
  • 2020-01-31: End-to-end MLIR Workflow in IREE: MLIR Open Design Meeting Presentation (recording and slides)

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.