Drop `--iree-llvmcpu-enable-microkernels`, replaced by `--iree-llvmcpu-enable-ukernels` (#15646)

This old flag (`-microkernels`) was a boolean. The new flag
(`-ukernels`) is a string.

Porting guide:
- If you were passing `--iree-llvmcpu-enable-microkernels` (or
equivalently, `...=true`), the equivalent new flag is
`--iree-llvmcpu-enable-ukernels=all`. You may however choose to do
`--iree-llvmcpu-enable-ukernels=mmt4d` instead if you want to only
enable the mmt4d ukernel and not all future ukernels that may be added
in the future.
- If you were passing `--iree-llvmcpu-enable-microkernels=false`, that
was the default behavior anyway so that wasn't having any effect, so you
could drop that; however, if you meant to explicitly opt out of ukernels
whenever they would become default, the equivalent of that with the new
flag is `--iree-llvmcpu-enable-ukernels=none`.

All occurences of the old flag in the IREE repo have already been
replaced. Please confirm when it's OK to proceed with this, @mariecwhite
@pzread @dcaballe @jpienaar @lundong @hcindyl @banach-space .
1 file changed
tree: ac814aa02a4d2a0a8f942510d01680327d44ea73
  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. Testing/
  13. tests/
  14. third_party/
  15. tools/
  16. .bazel_to_cmake.cfg.py
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .dockerignore
  22. .git-blame-ignore-revs
  23. .gitignore
  24. .gitmodules
  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

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.