Switching code to use FunctionOpInterface instead of FuncOp.
There's lots of tech debt around func.func, it turns out. As many
uses of func (besides creation) have been switched to the
FunctionOpInterface as a first step toward support non-func dialects.
These changes will also allow more passes to correctly operate on
initializers and future dispatch export ops that carry more
information than func.func allows. Codegen is welcome to keep using
func where it wants as it's more aligned with upstream than the rest
of the compiler but there was a lot of unnecessary coupling to func
that predated the existence of the FunctionOpInterface/CallOpInterface
this cleans up.

There's a few places that still rely on func that don't really need
it but they aren't trivial to switch and the hope is that the bulk
of the cleanup here (passes, basic walks/iteration, etc) will make
them easier to burn down now that they are the exception rather than
the rule.

Progress on #16187.
565 files changed
tree: 7ddd1f1476e724d35f95f9df923c7ff7cfc11a18
  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.