Google Git
Sign in
opensecura / 3p / openxla / iree / 886ac3e269454180b149abd68e230ca079a3744a
commit886ac3e269454180b149abd68e230ca079a3744a[log] [tgz]
authorbjacob <benoitjacob@google.com>Tue Mar 07 14:25:01 2023 -0500
committerGitHub <noreply@github.com>Tue Mar 07 14:25:01 2023 -0500
treedf37444e6154c5a0aaaf15a8ecb684d9c35ec2d8
parentf1bbc5703cd907133b885e5807a09bd1afd5d3b8 [diff]
Centralize CPU features, fix `iree_cpu_lookup_data_by_key`, add a `iree-cpuinfo` tool (#12498)

The starting point of this PR was that I realized that I had forgotten
to update `iree_cpu_lookup_data_by_key`.

That sent me looking for a way to have it automatically sync'd with the
rest of the code, resulting in the present `.inl` approach.

As a bonus, I added a `iree-cpuinfo` tool, also automatically sync'd
with the `.inl` and just a few lines of impl. This is a quick debugging
tool allowing to answer quickly the question "which CPU features are we
actually detecting on this machine". Obviously the point is not provide
the best CPU feature detection tool, the point is that it's by
construction bug-for-bug equivalent to IREE's actual CPU feature
detection.
9 files changed
tree: df37444e6154c5a0aaaf15a8ecb684d9c35ec2d8
  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.