Google Git
Sign in
opensecura / 3p / openxla / iree / 1bc316228ec65779641445653bbc6e3d5841f399
commit1bc316228ec65779641445653bbc6e3d5841f399[log] [tgz]
authorGeoffrey Martin-Noble <gcmn@google.com>Tue May 16 16:14:43 2023 -0700
committerGitHub <noreply@github.com>Tue May 16 23:14:43 2023 +0000
tree74d1ed9905034a3a41110995c6981ccfb4111284
parentc1b424c8b7304da5a5aa06599d7fd449822b15ab [diff]
Make Discord notification link directly to workflow run (#13646)

This makes the title a URL that takes you to the thing you actually
want to see: the failing run. Currently the closest thing is the checks
page, which is super noisy for commits on main because all the stuff
running on `schedule` or `pull_request_target` run in the context of
the HEAD commit on main and apparently post all their checks there...

I tried also making the message less noisy in general, but it removed
too much context. If we want something different, we'll have to switch
to a different action: this one deliberately already has everything
formatted for you. Although really I'd love to figure out a way we can
use issues for CI failures. Discord kind of sucks for tracking.
1 file changed
tree: 74d1ed9905034a3a41110995c6981ccfb4111284
  1. .devcontainer/
  2. .github/
  3. benchmarks/
  4. build_tools/
  5. compiler/
  6. docs/
  7. experimental/
  8. integrations/
  9. lib/
  10. llvm-external-projects/
  11. runtime/
  12. samples/
  13. tests/
  14. third_party/
  15. tools/
  16. .bazel_to_cmake.cfg.py
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .dockerignore
  22. .gitignore
  23. .gitmodules
  24. .pylintrc
  25. .style.yapf
  26. .yamllint.yml
  27. AUTHORS
  28. BUILD.bazel
  29. CITATION.cff
  30. CMakeLists.txt
  31. configure_bazel.py
  32. CONTRIBUTING.md
  33. LICENSE
  34. README.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.

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.