[Codegen][CPU] Register embedded ukernel bitcode + provider lookup. (#24568)

Wires the LLVMCPU plugin and the `#iree_cpu.ukernel_provider` attribute
to actually resolve ukernel bitcode:

* On plugin init, the embedded `iree_uk_cpu_bitcode` TOC is iterated and
each `.bc` is added to the global `EmbeddedDataDirectory` (mirrors
`addAMDGPUUkernelBitcodeToGlobalEmbeddedDataDirectory` in
`ROCMTarget.cpp`).

* `UKernelProviderAttr::createAndReplaceWithUkernelOp` now resolves the
bitcode by name: user-supplied `hal.executable.objects` ancestors first
(BYO and BYO-override paths), then the embedded directory. If found and
not already on the op, the attribute is attached to the source op; the
default `LowerBitcodeUKernelsPass` rewrite then preserves it on the
resulting `ukernel.generic`. The provider still returns `std::nullopt`
for the rewrite itself — specialized `inner_tiled` handling (scalar
`intrinsics_{m,n,k}` + outer K count + ACC inner stride) lands with
SelectUKernels in a follow-up.

* Filename match is `<ukernelName>.<features>.bc` (or bare
`<ukernelName>.bc`), matching the build rules under
`compiler/plugins/target/LLVMCPU/builtins/ukernel/`. Multi-variant
disambiguation by target feature set also lands with SelectUKernels.

BUILD.bazel: LLVMCPU plugin gains a dep on

`//compiler/plugins/target/LLVMCPU/builtins/ukernel:iree_uk_cpu_bitcode`,
and the `iree_cpu` dialect picks up HAL IR + `EmbeddedDataDirectory` so
the provider implementation can live with the attribute (consistent with
how `ROCMUkernelBitcodeSupport.cpp` sits inside the ROCM dialect).

Tests: a three-way lit test (`lookup_builtin_and_byo.mlir`) covers each
branch of the lookup:
1. Built-in only — no user objects; expect a `dense_resource<…>` with
the embedded bf16 bitcode (2732 bytes) attached.
2. BYO override — user supplies bitcode under the built-in's filename;
expect the user's bytes to flow through unchanged (and CHECK-NOT against
`dense_resource` to catch a regression where the provider silently swaps
in the embedded copy).
3. Pure BYO — user-only name with no matching built-in; expect the
user's bitcode to surface on the rewritten op.

Progress towards https://github.com/iree-org/iree/issues/24574.

Signed-off-by: Benoit Jacob <jacob.benoit.1@gmail.com>
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
9 files changed
tree: 87300461be652460866e2c27f7618efd451387fb
  1. .github/
  2. build_tools/
  3. compiler/
  4. docs/
  5. experimental/
  6. integrations/
  7. lib/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazel_to_cmake.cfg.py
  15. .bazelignore
  16. .bazelrc
  17. .bazelversion
  18. .clang-format
  19. .git-blame-ignore-revs
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .pre-commit-config.yaml
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. MAINTAINERS.md
  33. MODULE.bazel
  34. README.md
  35. RELEASING.md
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.

IREE Discord Status pre-commit OpenSSF Best Practices

Project news

Project status

Release status

Releases notes are published on GitHub releases.

PackageRelease status
GitHub release (stable)GitHub Release
GitHub release (nightly)GitHub Release
iree-base-compilerPyPI version
iree-base-runtimePyPI version

For more details on the release process, see https://iree.dev/developers/general/release-management/.

Build status

CI PkgCI

Nightly build status

Operating systemBuild status
LinuxCI - Linux arm64 clang
macOSCI - macOS x64 clang
macOSCI - macOS arm64 clang

For the full list of workflows see https://iree.dev/developers/general/github-actions/.

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

Community meeting recordings: IREE YouTube channel

DateTitleRecordingSlides
2025-06-10Data-Tiling in IREE: Achieving High Performance Through Compiler Design (AsiaLLVM)recordingslides
2025-05-17Introduction to GPU architecture and IREE's GPU CodeGen Pipelinerecordingslides
2025-02-12The Long Tail of AI: SPIR-V in IREE and MLIR (Vulkanised)recordingslides
2024-10-01Unveiling the Inner Workings of IREE: An MLIR-Based Compiler for Diverse Hardwarerecording
2021-06-09IREE Runtime Design Tech Talkrecordingslides
2020-08-20IREE CodeGen (MLIR Open Design Meeting)recordingslides
2020-03-18Interactive HAL IR Walkthroughrecording
2020-01-31End-to-end MLIR Workflow in IREE (MLIR Open Design Meeting)recordingslides

License

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