Google Git
Sign in
opensecura / 3p / openxla / iree / 4a2c2142958f9b5263e787b77afe15a55008e6d1
commit4a2c2142958f9b5263e787b77afe15a55008e6d1[log] [tgz]
authorScott Todd <scotttodd@google.com>Wed May 17 20:00:44 2023 -0700
committerGitHub <noreply@github.com>Wed May 17 20:00:44 2023 -0700
tree7aab7934ddedb35eb40c574e4c89353642f24866
parent098764ea5298669b1e991cd0701dc248fdc21b47 [diff]
Convert all website reference links to inline links. (#13671)

I noticed a broken link here:
https://openxla.github.io/iree/deployment-configurations/gpu-cuda-rocm/#download-compiler-as-python-package
(oops - https://github.com/openxla/iree/pull/12106)

![image](https://github.com/openxla/iree/assets/4010439/eae4b479-4ce2-4492-aabf-3f2a73c682a8)

These reference links are difficult to maintain if we're inconsistent in
their use. The linter we're using now technically supports analyzing
them, but it does not see through content blocks (a markdown extension
used by mkdocs). From what I can tell, reference links are pitched as a
way to save character counts when repeating links and to make paragraphs
smaller in the source. Neither of those are good reasons to compromise
on tooling support for identifying dead links, and broken inline links
are much easier to spot manually.
5 files changed
tree: 7aab7934ddedb35eb40c574e4c89353642f24866
  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.