Google Git
Sign in
opensecura / 3p / openxla / iree / f1545bb6b5c73ff06fcc59cf3bf40c4002ef1d26
commitf1545bb6b5c73ff06fcc59cf3bf40c4002ef1d26[log] [tgz]
authorbjacob <benoitjacob@google.com>Fri May 26 13:11:40 2023 -0400
committerGitHub <noreply@github.com>Fri May 26 13:11:40 2023 -0400
tree0ca28fd62eb474e9323732cbe901b0f14db493ea
parent61551c002eba29b2f8abf23f73850378a0b0ead1 [diff]
move CUDA check tests out of e2e/matmul (#13805)

This is the only check-test in this directory, everything else is
generated-trace-runner tests. Also the only checked-in .mlir file,
everything else is generated. So it's a bit out of place and fits better
in some other subdir below e2e/.

My selfish motivation here is that for #13804 I am going to need to run
this command: `bazel test //tests/e2e/matmul:*` . And it's really hard
to get it to work as there is this CUDA test here. Does CUDA work in
local Bazel builds for anyone outside of CI?

Note- there are CUDA tests in the e2e matmul tests, but those are really
CMake-only - the Bazel implementation in `iree_trace_runner_test.bzl` is
currently skipping CUDA, which is why they are not problematic for me.
5 files changed
tree: 0ca28fd62eb474e9323732cbe901b0f14db493ea
  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.