Google Git
Sign in
opensecura / 3p / openxla / iree / 4fddac063bf413945fbde6b55ebcf392e0901717
commit4fddac063bf413945fbde6b55ebcf392e0901717[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Wed May 29 17:30:38 2024 -0700
committerGitHub <noreply@github.com>Wed May 29 17:30:38 2024 -0700
tree88a72d0b66749c5651341054f9967830112558ee
parentb6b1df625ebf0249aa9a420642c31ae81b23dee4 [diff]
Merge build_test_runtime jobs into a single matrix. (#17509)

This folds the three 'build_test_runtime' jobs (Linux x86, Linux arm64,
Windows) into a single matrix with most steps shared. I'm similarly
planning on merging more jobs using matrices:
https://github.com/iree-org/iree/issues/17136.

This does limit how "CI behavior manipulation"
(https://iree.dev/developers/general/contributing/#ci-behavior-manipulation)
works - for example now setting `ci-exactly: build_test_runtime` will
run these 3 jobs, and they cannot be run individually.

* A solution like
https://stackoverflow.com/questions/65384420/how-do-i-make-a-github-action-matrix-element-conditional
would be needed to keep the old behavior. We actually have a version of
that already in the `generate_matrix` step of
https://github.com/iree-org/iree/blob/main/.github/workflows/benchmark_execution.yml
(sample logs:
https://github.com/iree-org/iree/actions/runs/9214012269/job/25350287269),
but I have mixed feelings about the complexity involved there.
1 file changed
tree: 88a72d0b66749c5651341054f9967830112558ee
  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. MAINTAINERS.md
  33. README.md
  34. RELEASING.md
  35. 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.