Google Git
Sign in
opensecura / 3p / openxla / iree / 9796d921a6b13f3a98bcce23acedabf764b73f3d
commit9796d921a6b13f3a98bcce23acedabf764b73f3d[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Thu Apr 04 14:17:16 2024 -0700
committerGitHub <noreply@github.com>Thu Apr 04 14:17:16 2024 -0700
tree75f53395a819fcb2c982565f01deeb13dec52655
parent5ad0fe20279f838763277a15d4ef7e2124478b7f [diff]
Bump SHARK-TestSuite commit to include "keep going" change. (#16958)

This bumps to
https://github.com/nod-ai/SHARK-TestSuite/commit/e67779cee2a3878c2ba9ede50f2121cf21c1e99c.

* Previously, if compilation unexpectedly succeeded, a test case would
immediately XPASS. The process would then be to remove the test from
`expected_compile_failures`, run the test suite again, then possibly add
the test case back to `expected_run_failures` if the run fails.
* Now, if compilation unexpectedly succeeds, the 'run' test phase will
be attempted, so we can directly move the test from one XFAIL list to
the other, or at least know more confidently that the test is now fully
passing.

(Updating XFAIL lists could still be further automated, but this is an
incremental step in the right direction)
3 files changed
tree: 75f53395a819fcb2c982565f01deeb13dec52655
  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. .gitignore
  23. .gitmodules
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. README.md
  33. 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

License

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