Google Git
Sign in
opensecura / 3p / openxla / iree / b637a30b6514483e78cdcc45912e7891b8f1a000
commitb637a30b6514483e78cdcc45912e7891b8f1a000[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Mon Aug 19 08:27:47 2024 -0700
committerGitHub <noreply@github.com>Mon Aug 19 15:27:47 2024 +0000
treecac5845590da8a7cec3ed5819890533da6e3c06e
parentd5c63704b23cbba490d109c8dd309dfb2f78a205 [diff]
Refactor how `linux_x64_clang_debug` uses Docker and scripts. (#18255)

Progress on https://github.com/iree-org/iree/issues/15332 and
https://github.com/iree-org/iree/issues/18238 .

Similar to https://github.com/iree-org/iree/pull/18252, this drops a
dependency on the
[`build_tools/docker/docker_run.sh`](https://github.com/iree-org/iree/blob/main/build_tools/docker/docker_run.sh)
script. Unlike that PR, this goes a step further and also stops using
[`build_tools/cmake/build_all.sh`](https://github.com/iree-org/iree/blob/main/build_tools/cmake/build_all.sh).

Functional changes:
* No more building `iree-test-deps`
* We only get marginal value out of compiling test files using a debug
compiler
* Those tests are on the path to being moved to
https://github.com/iree-org/iree-test-suites
* No more ccache
* The debug build cache is too large for a local / GitHub Actions cache
* I want to limit our reliance on the remote cache at
`http://storage.googleapis.com/iree-sccache/ccache` (which uses GCP for
storage and needs GCP auth)
* Experiments show that this build is not significantly faster when
using a cache, or at least dropping `iree-test-deps` provides equivalent
time savings

Logs before:
https://github.com/iree-org/iree/actions/runs/10417779910/job/28864909582
(96% cache hits, 9 minute build but 19 minutes total, due to
`iree-test-deps`)
Logs after:
https://github.com/iree-org/iree/actions/runs/10423409599/job/28870060781?pr=18255
(no cache, 11 minute build)

ci-exactly: linux_x64_clang_debug

---------

Co-authored-by: Marius Brehler <marius.brehler@gmail.com>
1 file changed
tree: cac5845590da8a7cec3ed5819890533da6e3c06e
  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.