Integrate llvm-project and bump dependencies. (#12562)

* llvm-project: e510d0bda0876c4baa3a270dca39b95da7ec6d9e
* mlir-hlo: e86610442f58b889a57bf814d75c4b50c769c2a3
* tensorflow: 67ba341c869e30ee4a89e040cd875d12b9bc666e

Cherry-picked from LLVM:
```
commit 80074d5fc0ab3f165865b15f5bf55ffac0917bcd (HEAD -> integrate-3-8-2023, fork/integrate-3-8-2023)
Author: Matthias Springer <me@m-sp.org>
Date:   Fri Mar 10 11:25:15 2023 +0100

    [mlir][NFC] reifyResultShapes: Add extra error checking
    
    This change adds a new helper function `mlir::reifyResultShapes` that calls the corresponding interface method and also checks the result produced by the implementation when running in debug mode. Bugs due to incorrect interface implementations can be difficult to debug.
    
    This helper function also reduces the amount of code needed at call sites: the cast to `ReifyRankedShapedTypeOpInterface` is done in the helper function.
    
    Differential Revision: https://reviews.llvm.org/D145777

commit 32b15f601de173e9511f470f7423108d3154e582
Author: Matthias Springer <me@m-sp.org>
Date:   Fri Mar 10 11:24:43 2023 +0100

    [mlir][tensor/linalg] Fix bug in reifyResultShapes
    
    `reifyResultShapes` should return an IntegerAttr if and only if the corresponding dimension is static.
    
    Differential Revision: https://reviews.llvm.org/D145702

commit 894555cd6adf2e0faffe713373a266650b40bb4e
Author: David Green <david.green@arm.com>
Date:   Wed Mar 8 12:48:21 2023 +0000

    [AArch64] Fix load-insert-zero patterns with i8 and negative offsets.
    
    These should have been using the LDURBi instructions where the offset is
    negative, as reported from the reproducer in D144086.
```

Created a new commit on iree-mlir-hlo fork:


https://github.com/iree-org/iree-mhlo-fork/commit/b14e9d9b06255e4476f5698e3bfc531dec793ded
22 files changed
tree: 2096ab84e16216a2cc47a70c4b209536c2728e07
  1. .github/
  2. benchmarks/
  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. .bazelignore
  16. .bazelrc
  17. .bazelversion
  18. .clang-format
  19. .dockerignore
  20. .gitignore
  21. .gitmodules
  22. .pylintrc
  23. .style.yapf
  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

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.