Google Git
Sign in
opensecura / 3p / openxla / iree / e45c570997586d327ca78342f3644f0c134d88ea
commite45c570997586d327ca78342f3644f0c134d88ea[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Tue Oct 01 13:24:36 2024 -0700
committerGitHub <noreply@github.com>Tue Oct 01 13:24:36 2024 -0700
tree33d1576ffec862574140a2840c4364eb29264ab6
parent839f7f6e42942395b23de5ba1c470c26bd468e0b [diff]
Switch linux_arm64_clang workflow to arm-hosted runner. (#18643)

Context:
https://github.com/iree-org/iree/issues/18238#issuecomment-2383652809

This uses https://gitlab.arm.com/tooling/gha-runner-docs to run on Arm
Hosted GitHub Action (GHA) Runners, instead of the runners that Google
has been hosting. Note that GitHub also offers Arm runners, but they are
expensive and require a paid GitHub plan to use
(https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners/about-larger-runners).

For now this is continuing to run nightly, but we could also explore
running more regularly if Arm wants and approves. We'd want to figure
out how to use a build cache efficiently for that though. We can use
sccache storage on Azure, but there might be charges between Azure and
AWS for the several gigabytes of data moving back and forth. If we set
up a dedicated cache server
(https://github.com/iree-org/iree/issues/18557), we'll at least have
more visibility into and control over the storage and compute side of
billing.

Test runs:
* https://github.com/iree-org/iree/actions/runs/11114007934 (42 minutes)
* https://github.com/iree-org/iree/actions/runs/11114658487 (40 minutes)
* https://github.com/iree-org/iree/actions/runs/11114757082 (38 minutes)
* https://github.com/iree-org/iree/actions/runs/11128634554 (40 minutes)

skip-ci: no impact on other builds
1 file changed
tree: 33d1576ffec862574140a2840c4364eb29264ab6
  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. .git-blame-ignore-revs
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .pre-commit-config.yaml
  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.

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.