Google Git
Sign in
opensecura / 3p / openxla / iree / f8efefed13364fe29fd36dc137c84529fc6707ba
commitf8efefed13364fe29fd36dc137c84529fc6707ba[log] [tgz]
authorbjacob <benoitjacob@google.com>Tue Feb 28 15:28:31 2023 -0500
committerGitHub <noreply@github.com>Tue Feb 28 20:28:31 2023 +0000
tree7c0ca1ec31fc10df36a08053e3da6d31dcfc9ec8
parent26fc3994d95e55b6c5bb4f760d64470cea67b5da [diff]
Rework `cpu.c` to make room for x86 path (#12395)

The main change is to switch the nesting of the `#if`'s. This used to be
first `#if` on platform/OS, then `#if` on CPU architecture. But actually
the fact that the platform/OS needs to be involved is a ARM-ism; it is
the CPU architecture that drives the higher level approach. And
structuring the code this way makes it possible to later split it into
separate files for each architecture (not doing it for now because this
opens questions of what we do with the Bazel+CMake build system, so
deferring that until there's a concrete need).

And even for the existing code, having the `#if` on CPU architecture at
the top results in simplification as a couple of platform/OS-centric
functions don't need a fallback anymore now that they only exist within
a CPU-architecture-specific section.

Also flattened some helpers, IMO making code more readable.

Also renamed cpu_data identifiers to be shorter.
11 files changed
tree: 7c0ca1ec31fc10df36a08053e3da6d31dcfc9ec8
  1. .github/
  2. benchmarks/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazelignore
  15. .bazelrc
  16. .bazelversion
  17. .clang-format
  18. .dockerignore
  19. .gitignore
  20. .gitmodules
  21. .pylintrc
  22. .style.yapf
  23. .yamllint.yml
  24. AUTHORS
  25. BUILD.bazel
  26. CITATION.cff
  27. CMakeLists.txt
  28. configure_bazel.py
  29. CONTRIBUTING.md
  30. LICENSE
  31. README.md
  32. 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.