Drop conditionals and configured headers from the ukernels build (#13834)

This drop CMake `if()` and configured headers from the ukernels build.
Instead:

* The uarch-specific code paths are unconditionally added and then
`#if`'d out inside C code based on compiler version macros. This
simplifies the build ahead of multi-arch bitcode (#13804) and paves the
way for Bazel support on par with CMake.
* The `iree_uk_ssize_t` type is unconditionally `int64_t`, being more
clearly branded a size/index type more than a "pointer-size" type. This
wasn't completely clear until the recent bitcode push, but now that I'm
looking at LLVM IR where `ptr` is an opaque type and there isn't even a
concept of pointer size, while size/index have to use some explicitly
sized integer type, this change reflects the reality of what this type
is used for. It would be possible to make this `int32_t` instead of
`int64_t` for best performance on 32-bit architectures but for now
making it unconditionally `int64_t` is an easy first step and keeps what
we were currently doing in standalone builds.
39 files changed
tree: b9eae846cb98892987dc018d934b7df64de5c0a5
  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. .gitignore
  22. .gitmodules
  23. .pylintrc
  24. .style.yapf
  25. .yamllint.yml
  26. AUTHORS
  27. BUILD.bazel
  28. CITATION.cff
  29. CMakeLists.txt
  30. configure_bazel.py
  31. CONTRIBUTING.md
  32. LICENSE
  33. README.md
  34. 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.