[LLVMCPU] Fix ArmSME requiring classic SVE, breaking SME-only targets (e.g., Apple Silicon) (#24661) `enableAArch64SME` required `hasAnySVEFeature` in addition to `hasSMEFeature`, even though SME runs in Streaming SVE mode and does not architecturally need classic (non-streaming) SVE. On SME-only targets (e.g. Apple Silicon, which implements `FEAT_SME`/`FEAT_SME2` but not `FEAT_SVE`), this meant: - **`+sme` alone**: `enableAArch64SME` was `false`, so the ArmSME lowering pipeline never ran. Vectorization silently fell back to scalar code, but a leftover `vscale` was never inside a function marked "streaming", so it had no legal instruction-selection pattern: `iree-compile` crashed with `LLVM ERROR: Cannot select: vscale`. - **`+sve,+sme` together** (the only combination the existing SME e2e tests use): compiles fine, but a separate, Darwin-specific mechanism in `AArch64FrameLowering`/`AArch64PrologueEpilogue` is gated on `hasSVE()`. With `+sve` set, LLVM emits `cntd` directly in the function prologue *before* `smstart`, which is illegal on hardware without non-streaming SVE and crashes at runtime with `SIGILL`. Neither combination worked; does that mean that, prior to this PR, it wasn't possible to use IREE's SME support on this class of hardware? If so, it implies that, until now, IREE couldn't leverage SME on Apple M4 Pro processors. But I feel like I might be missing something... Fixes #24660. See: https://github.com/llvm/llvm-project/issues/204853 @banach-space @egebeysel @AGindinson @maxbartel --------- Signed-off-by: Federico Bruzzone <federico.bruzzone.i@gmail.com> Co-authored-by: Ege Beysel <beyselege@gmail.com>
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.
Releases notes are published on GitHub releases.
| Package | Release status |
|---|---|
| GitHub release (stable) | |
| GitHub release (nightly) | |
iree-base-compiler | |
iree-base-runtime |
For more details on the release process, see https://iree.dev/developers/general/release-management/.
| Operating system | Build status |
|---|---|
| Linux | |
| macOS | |
| macOS |
For the full list of workflows see https://iree.dev/developers/general/github-actions/.
See our website for more information.
Community meeting recordings: IREE YouTube channel
| Date | Title | Recording | Slides |
|---|---|---|---|
| 2025-06-10 | Data-Tiling in IREE: Achieving High Performance Through Compiler Design (AsiaLLVM) | recording | slides |
| 2025-05-17 | Introduction to GPU architecture and IREE's GPU CodeGen Pipeline | recording | slides |
| 2025-02-12 | The Long Tail of AI: SPIR-V in IREE and MLIR (Vulkanised) | recording | slides |
| 2024-10-01 | Unveiling the Inner Workings of IREE: An MLIR-Based Compiler for Diverse Hardware | recording | |
| 2021-06-09 | IREE Runtime Design Tech Talk | recording | slides |
| 2020-08-20 | IREE CodeGen (MLIR Open Design Meeting) | recording | slides |
| 2020-03-18 | Interactive HAL IR Walkthrough | recording | |
| 2020-01-31 | End-to-end MLIR Workflow in IREE (MLIR Open Design Meeting) | recording | slides |
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.