Google Git
Sign in
opensecura / 3p / openxla / iree / 4b01beb90efe01aff9d2e4d4aaa545d21f7077f6
commit4b01beb90efe01aff9d2e4d4aaa545d21f7077f6[log] [tgz]
authorGeoffrey Martin-Noble <gcmn@google.com>Tue Aug 16 14:52:53 2022 -0700
committerGitHub <noreply@github.com>Tue Aug 16 21:52:53 2022 +0000
treefd4553e5260b52603f041dcd25b3842369bd0236
parent58f477322a0f73a1823eb94ef1e78ecde3e9796c [diff]
Use string in PR description instead of label to skip CI (#10112)

As discussed in https://github.com/iree-org/iree/issues/10042, we
discovered that using a label doesn't work for the very important
case of when the PR is just created, so we're shifting to use the PR
body instead.

Tested: Created this PR with "skip-ci" as the entire body, which
resulted in correctly skipping the CI. Also added some additional lines
before and after, and CI was still correctly skipped. Finally, this PR
body as written contains the string, but not on its own line and CI is
not skipped.

Just skip-ci: https://github.com/iree-org/iree/runs/7866417853

With other content in the PR body:
![also_other_content](https://user-images.githubusercontent.com/5732088/184980308-ab8f1e90-453e-493c-9224-a10acdc5cc2b.png)
https://github.com/iree-org/iree/runs/7866417853
2 files changed
tree: fd4553e5260b52603f041dcd25b3842369bd0236
  1. .github/
  2. benchmarks/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazelignore
  15. .bazelrc
  16. .bazelversion
  17. .clang-format
  18. .gitignore
  19. .gitmodules
  20. .pylintrc
  21. .style.yapf
  22. .yamllint.yml
  23. AUTHORS
  24. BUILD.bazel
  25. CITATION.cff
  26. CMakeLists.txt
  27. configure_bazel.py
  28. CONTRIBUTING.md
  29. LICENSE
  30. README.md
  31. 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

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

  • 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.