Bump LLVM to llvm/llvm-project@730f498c961f (#16286)

- Revert llvm/llvm-project@2800448 locally because it crashes many the
RISC-V compilation. After raising it to the author, they reverted it
upstream.
- Revert llvm/llvm-project@66347e51 locally because it causes
regression. It is already reverted in upstream.
- The cuda matmul regression appears in the LLVM NVPTX backend. We are
generating the same LLVM bitcode before [converting to
ISA](https://github.com/openxla/iree/blob/861815c/compiler/plugins/target/CUDA/CUDATarget.cpp#L600);
CUDA perf is not our priority; we don't have folks super familiar with
that layer and it is quite involved fixing there. So we are fine taking
the hit for now and revisit later. (maybe later it'd be fixed in
upstream..)

Additional fixes:

- Apply fixes for
https://github.com/llvm/llvm-project/commit/ce7cc723b9d51ad9c741bbaeecb5e008b2b81338
- Apply fixes for
https://github.com/llvm/llvm-project/commit/b91bba89edfb25d011e1f2366cda5dec605c87f6

---------

Co-authored-by: Diego Caballero <diegocaballero@google.com>
Co-authored-by: Lei Zhang <antiagainst@gmail.com>
9 files changed
tree: b0cbe6dd1508c8c1214eb98849077b69d435c3ac
  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. .gitignore
  23. .gitmodules
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. README.md
  33. 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

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.