[Codegen][CPU] End-to-end-through-codegen lit test for ukernel framework. (#24571)

Closes the loop on the new C-bitcode ukernel framework with an
`iree-opt` lit test that drives the full LLVMCPU codegen pipeline on an
`inner_tiled` rooted dispatch wrapped in the standard
`hal.executable.variant` + binding-subspan structure, and asserts the
whole chain end-to-end:

- Bitcode reaches the dispatch's `hal.executable.variant` as a
first-class `objects(...)` attribute (the long-lived home).
- `llvm.func @iree_uk_mma_…` is declared with `hal.import.bitcode =
true`, the flag that tells `RewriteExternCallOpToDynamicImportCallOp` to
skip the runtime-import-table indirection.
- A direct `llvm.call @iree_uk_mma_…` replaces the original
`inner_tiled` — no `__import_ordinal_iree_uk_mma_…` (which would mean we
accidentally re-used the legacy runtime-resolved path), no leftover
`inner_tiled`, no leftover `ukernel.generic`.

To make that chain work, two pieces had to land alongside the test:

* `UKernelProviderAttr::createAndReplaceWithUkernelOp` now actually
builds the `UKernelGenericOp` (returning `success`, not `nullopt`),
setting `fn_def_attrs = {hal.import.bitcode = true}` on it. That flag
propagates onto the `func.func` declaration that
`LowerUKernelOpsToCalls` synthesizes, and through it onto the
`llvm.func` that `ConvertToLLVM` produces. Without this, the
"self-contained bitcode" property of the new framework would not hold —
every external call would be routed through the runtime import table
just like the legacy mmt4d ukernels.

* Bitcode lookup-and-attach is factored into a public helper
`IREE::CPU::attachUKernelBitcodeOnOp`, called both from
`LLVMCPUSelectUKernels` (at kernel-config time, mirroring GPU's
`ensureUKernelBitcodeAndFinalizeConfig`) and from the provider itself
(as a backstop for the BYO / hand-written-IR paths). It attaches the
bitcode both as a `hal.executable.objects` discardable attribute on the
op (the GPU-aligned shape) *and* directly on the enclosing
`hal.executable.variant`'s `objects` operand attribute (the durable
home, sidestepping passes that strip discardable attrs through
`ConvertToLLVM`).

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>
6 files changed
tree: 7265a23fcf2e13e59c078f00cdbd5d32936f6597
  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.