Google Git
Sign in
opensecura / 3p / openxla / iree / 59fbf3a19e65812a45b685ad56b72b03428aa234
commit59fbf3a19e65812a45b685ad56b72b03428aa234[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Fri Jun 07 14:13:25 2024 -0700
committerGitHub <noreply@github.com>Fri Jun 07 14:13:25 2024 -0700
tree84be672b1c1445c891e144ef7d70de95c1955ea1
parent7fc1a676c1c2464c7b9ab6f47c357a7803822f61 [diff]
Redirect submodules from shark-infra to iree-org. (#17614)

We moved these out of https://github.com/iree-org to make it easier for
project contributors to access them at a time when iree-org was defunct,
creating repos there took navigating an extraordinary amount of red
tape, and the main iree repo was in the https://github.com/openxla
GitHub org. Now that the iree repo is back in iree-org and we've updated
how we manage access, these repositories can move back too.

GitHub does some automatic redirecting but individual developers may
want to run `git submodule sync` after the repository moves and this
change. For developers working in the other repositories directly, run
`git submodule set-url [remote name] [new url]`. For example: `git
remote set-url origin https://github.com/iree-org/megabump.git`
3 files changed
tree: 84be672b1c1445c891e144ef7d70de95c1955ea1
  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. .git-blame-ignore-revs
  22. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .pre-commit-config.yaml
  26. .yamllint.yml
  27. AUTHORS
  28. BUILD.bazel
  29. CITATION.cff
  30. CMakeLists.txt
  31. configure_bazel.py
  32. CONTRIBUTING.md
  33. LICENSE
  34. MAINTAINERS.md
  35. README.md
  36. RELEASING.md
  37. 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.