[CUDA] Preserve executable export names independently from PTX symbols (#24889)

## Motivation

While testing [Qwen3.8-27B](https://huggingface.co/Qwen/Qwen3.8-27B)
end-to-end with IREE, I found a CUDA executable lookup failure.

## Summary

CUDA executable serialization sanitizes kernel names for PTX, but
previously used that same sanitized name as the IREE executable export
identity.

This breaks modules whose generated dispatch names contain characters
that are not valid PTX symbols, such as `$`. Turbine-exported modules
can contain names such as `forward$async_dispatch_*`: compilation
succeeds, but CUDA executable creation fails at runtime.

This change stores the original IREE export name separately from the
sanitized PTX kernel symbol:

- `kernel_name` remains the sanitized symbol used by
`cuModuleGetFunction`.
- `export_name` preserves the original name used by
`hal.executable.lookup.function`.

`export_name` is an appended optional FlatBuffer field. Updated runtimes
fall back to `kernel_name` when loading older VMFBs that do not contain
it.


## Minimal reproduction

A standalone IREE module with a public function containing `$`
reproduces the failure:

```mlir
func.func @qwen$prefill(%input: tensor<4xf32>) -> tensor<4xf32> {
  %output = tensor.empty() : tensor<4xf32>
  %result = linalg.generic {
      indexing_maps = [
        affine_map<(d0) -> (d0)>,
        affine_map<(d0) -> (d0)>
      ],
      iterator_types = ["parallel"]
    }
    ins(%input : tensor<4xf32>) outs(%output : tensor<4xf32>) {
      ^bb0(%in: f32, %out: f32):
        %scaled = arith.mulf %in, %in : f32
        linalg.yield %scaled : f32
    } -> tensor<4xf32>
  return %result : tensor<4xf32>
}
```

```
iree-compile repro.mlir \
  --iree-hal-target-backends=cuda \
  --iree-cuda-target=sm_120 \
  --iree-cuda-target-features=+ptx87 \
  -o repro.vmfb

iree-run-module \
  --module=repro.vmfb \
  --device=cuda \
  --function='qwen$prefill' \
  --input=4xf32=1
```

## Error
```
NOT_FOUND; function 'qwen$prefill' not found in executable
```
Changing only the public symbol to `@qwen_prefill` succeeds and produces
the expected result.

## Testing

Built `iree-compile` and `iree-run-module`, then ran the repro on CUDA
SM120 with PTX 8.7.
After this change it succeeds:

```text
EXEC @qwen$prefill
result[0]: hal.buffer_view
4xf32=1 1 1 1
```

Signed-off-by: weimin023 <tnwilly@gmail.com>
3 files changed
tree: 80a1713b2bf8e7286bf567475ecf600c2f0d646a
  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. GOVERNANCE.md
  32. LICENSE
  33. MAINTAINERS.md
  34. MODULE.bazel
  35. README.md
  36. 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 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.