Google Git
Sign in
opensecura / 3p / openxla / iree / 860026f53714edfa3e1798d5dd58edc74dd536d5
commit860026f53714edfa3e1798d5dd58edc74dd536d5[log] [tgz]
authorLevon Ter-Grigoryan <leonidusspartus@gmail.com>Fri Jun 09 19:44:56 2023 +0200
committerGitHub <noreply@github.com>Fri Jun 09 13:44:56 2023 -0400
tree663bf8f93c835c342968d66e2a234630d9a11583
parent5c0fc03100e63f2e18097cdad7a5d00c294b425a [diff]
Declare exported headers to Bazel to fix `bazel build --incompatible_no_implicit_file_export` (#13982)

Files exported to other Bazel packages need to be explictly declared
with
[`exports_files`](https://bazel.build/reference/be/functions#exports_files).
This was currently relying on the legacy behavior of implict exporting
of inputs to other rules, so this was failing to build with the stricter
behavior enabled by `--incompatible_no_implicit_file_export`.

---------

Co-authored-by: Benoit Jacob <benoitjacob@google.com>
5 files changed
tree: 663bf8f93c835c342968d66e2a234630d9a11583
  1. .devcontainer/
  2. .github/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. lib/
  9. llvm-external-projects/
  10. runtime/
  11. samples/
  12. tests/
  13. third_party/
  14. tools/
  15. .bazel_to_cmake.cfg.py
  16. .bazelignore
  17. .bazelrc
  18. .bazelversion
  19. .clang-format
  20. .dockerignore
  21. .gitignore
  22. .gitmodules
  23. .pylintrc
  24. .style.yapf
  25. .yamllint.yml
  26. AUTHORS
  27. BUILD.bazel
  28. CITATION.cff
  29. CMakeLists.txt
  30. configure_bazel.py
  31. CONTRIBUTING.md
  32. LICENSE
  33. README.md
  34. 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

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

  • 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.