Google Git
Sign in
opensecura / 3p / openxla / iree / 561230733571817e666c415aa00db1c8478a8089
commit561230733571817e666c415aa00db1c8478a8089[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Mon Sep 16 08:22:31 2024 -0700
committerGitHub <noreply@github.com>Mon Sep 16 08:22:31 2024 -0700
treee2ccec17b429cea1297fb960a0efc2150dd3b245
parent600cec4ea1a185d521ddb3076353de82f05a52ba [diff]
Disable workflows still relying on GCP self-hosted runners. (#18526)

See https://github.com/iree-org/iree/issues/18238.

We've finished migrating most load bearing workflows to use a new
cluster of self-hosted runners. These workflows are still using GCP
runners and are disabled:

* `build_test_all_bazel`: this may work on the new cluster using the
existing `gcr.io/iree-oss/base-bleeding-edge` dockerfile, but it uses
some remote cache storage on GCP and I want to migrate that to
https://github.com/iree-org/base-docker-images/. Need to take some time
to install deps, evaluate build times with/without a remote cache, etc.
* `test_nvidia_t4`, `nvidiagpu_cuda`, `nvidiagpu_vulkan`: we'll try to
spin up some VMs in the new cluster / cloud project with similar GPUs.
That's a high priority for us, so maybe within a few weeks.

Additionally, these workflows are still enabled but we should find a
longer term solution for them:

* `linux_arm64_clang` this is still enabled in code... for now. We can
disable
https://github.com/iree-org/iree/actions/workflows/ci_linux_arm64_clang.yml
from the UI
* arm64 packages are also still enabled:
https://github.com/iree-org/iree/blob/cc891ba8e7da3a3ef1c8650a66af0aa53ceed06b/.github/workflows/build_package.yml#L46-L50
5 files changed
tree: e2ccec17b429cea1297fb960a0efc2150dd3b245
  1. .github/
  2. build_tools/
  3. compiler/
  4. docs/
  5. experimental/
  6. integrations/
  7. lib/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazel_to_cmake.cfg.py
  15. .bazelignore
  16. .bazelrc
  17. .bazelversion
  18. .clang-format
  19. .dockerignore
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .pre-commit-config.yaml
  25. .yamllint.yml
  26. AUTHORS
  27. BUILD.bazel
  28. CITATION.cff
  29. CMakeLists.txt
  30. configure_bazel.py
  31. CONTRIBUTING.md
  32. LICENSE
  33. MAINTAINERS.md
  34. README.md
  35. RELEASING.md
  36. 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.

IREE Discord Status pre-commit OpenSSF Best Practices

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

Release status

PackageRelease status
GitHub release (stable)GitHub Release
GitHub release (nightly)GitHub Release
Python iree-compilerPyPI version
Python iree-runtimePyPI version

Build status

CI PkgCI

Host platformBuild status
LinuxCI - Linux x64 clang
CI - Linux arm64 clang
macOSCI - macOS x64 clang
WindowsCI - Windows x64 MSVC

For the full list of workflows see https://iree.dev/developers/general/github-actions/.

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.