Standardizes CMake setup of C directory trees behind a macro. (#16011)

This was done 3-5 different ways in tree and even more out of tree. With
the new install/exports stuff being very sensitive to making sure that
everything gets exported properly, it becomes more imperative that this
always works more by default.

I needed to fix this for an out of tree project which needed to adapt to
export sets, so I just decided to do it nicely for everyone.

Apparently having these implicit deps as `iree_cc_library`'ies was
really fouling up compiler warning flag generation for unknown reasons.
We've definitely been running with degraded warnings. I fixed the things
that this uncovered.

I'm going to go ahead and land this because I have a broken downstream
and the implications of having these warning flags wrong is frightening.
Then I'll revert locally and try to root cause what mystical thing is
actually going on. Definitely don't want to accidentally get back into
this state.
13 files changed
tree: f1ebff71daedfebcbf95b3aaecad5e9bc085f782
  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

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.