Google Git
Sign in
opensecura / 3p / openxla / iree / 7a29e8ec34053e0008926e407ac0fb48e25d14e0
commit7a29e8ec34053e0008926e407ac0fb48e25d14e0[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Mon Jul 08 15:54:24 2024 -0700
committerGitHub <noreply@github.com>Mon Jul 08 15:54:24 2024 -0700
tree314b0298369b633d7b0a0cf9f64f94032bb1831b
parent96c9bfb66cf24883f359d051281cc99d10a7a69e [diff]
Switch Linux x86 package builds to use standard runners. (#17822)

For some reason the runners tagged `managed-releaser, os-family=Linux,
runner-group=releaser` aren't picking up jobs on
https://github.com/iree-org/iree/actions/workflows/build_package.yml
(discussion [here on
Discord](https://discord.com/channels/689900678990135345/1259913154620686581/1259916287069523969)).
Rather than troubleshoot those runners, we can just switch to standard
GitHub-hosted runners and accept longer build times for these daily
builds.

Tested here: https://github.com/iree-org/iree/actions/runs/9844299015
(3h30m runs, about the same as macOS and Windows).

skip-ci: not tested by presubmit
1 file changed
tree: 314b0298369b633d7b0a0cf9f64f94032bb1831b
  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. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .pre-commit-config.yaml
  26. .yamllint.yml
  27. AUTHORS
  28. BUILD.bazel
  29. CITATION.cff
  30. CMakeLists.txt
  31. configure_bazel.py
  32. CONTRIBUTING.md
  33. LICENSE
  34. MAINTAINERS.md
  35. README.md
  36. RELEASING.md
  37. 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.