Google Git
Sign in
opensecura / 3p / openxla / iree / c20535560e71c85ea325f3582692b020edb8b236
commitc20535560e71c85ea325f3582692b020edb8b236[log] [tgz]
authorbjacob <benoitjacob@google.com>Tue Apr 18 14:57:21 2023 -0400
committerGitHub <noreply@github.com>Tue Apr 18 18:57:21 2023 +0000
tree50cfa59c276d7ce58d6f8468e844711b5a1c8c0e
parent0c3a30e2aadd841850901623ff601b136c7c595c [diff]
fatal non-numerical errors in e2e matmul test (#13139)

In #11077, we are looking at strange errors in these tests on Windows
with no specific numerical error output. `do_matmul_and_check_results`
is where we do all the heavy lifting with `iree_vm_` calls that could
fail. We do ultimately report the failure status from there, but farther
from the root cause than necessary. Deferring errors is useful for
numerical errors as it allows us to rerun on simpler matrices to
pinpoint the exact degree of generality that reproduces the error. But
for non-numerical errors, we should just treat all errors as fatal -- if
say a `iree_vm_invoke` fails, we want to debug straight into that.
1 file changed
tree: 50cfa59c276d7ce58d6f8468e844711b5a1c8c0e
  1. .github/
  2. benchmarks/
  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.