Add C++ static runner for CoreML

[metascroy]

Summary

Add a C++ runner for static attention CoreML LLM models exported with export_static_llm_coreml.py. This runner:

• Extends TextDecoderRunner from executorch/extension/llm/runner/text_decoder_runner.h
• Uses existing StaticAttentionIOManager from executorch/examples/models/llama/runner/static_attention_io_manager.h for KV cache management
• Auto-detects model configuration (input_len, cache_len, n_layers, n_kv_heads, head_dim, vocab_size, generate_full_logits) from model metadata
• Supports both regular greedy decoding and lookahead (speculative) decoding
• Processes prompts in chunks during prefill

New files:

• examples/apple/coreml/llama/runner/static_llm_runner.h - Runner header with StaticLLMConfig, StaticLLMIOManager, StaticLLMTextDecoderRunner, and StaticLLMRunner classes
• examples/apple/coreml/llama/runner/static_llm_runner.cpp - Runner implementation
• examples/apple/coreml/llama/runner/main.cpp - CLI entry point with gflags
• examples/apple/coreml/llama/runner/CMakeLists.txt - CMake build configuration
• examples/apple/coreml/llama/runner/build_and_run.sh - Build and run helper script

Modified files:

• CMakeLists.txt - Add subdirectory for static LLM CoreML runner (when EXECUTORCH_BUILD_EXTENSION_LLM_RUNNER, EXECUTORCH_BUILD_COREML, and APPLE are enabled)
• examples/apple/coreml/llama/export_static_llm_coreml.py - Add --cpu_only flag for CI testing (ANE not accessible in CI) and --no_generate_full_logits flag for more efficient models
• .ci/scripts/test_ane_static_llama.sh - Build and test the C++ runner in CI

Known issue: Lookahead decoding currently produces incorrect output (<unk> tokens) for stories110M, but does work for llama1B. This will be addressed in a follow-up PR.

Test plan

CI script .ci/scripts/test_ane_static_llama.sh tests:

1. Export static ANE model and CPU-only model
2. Build C++ runner with CMake/Ninja
3. Run regular decoding and validate output contains expected prefix "Once upon a time, there was"
4. Run lookahead decoding (runs without crashing, but output is incorrect - known issue)

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16463

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 6 New Failures, 3 Unrelated Failures

As of commit ff8ae0b with merge base 913436a ():

NEW FAILURES - The following jobs have failed:

• Apple / build-benchmark-app / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 65
• Apple / build-frameworks-ios / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 65
• Build Presets / apple (ios) / build (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 65
• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 6c871d30a664c4b88a0c3fc70dd3ed7e77195087d7bb92d5fc051108f6284464 /exec failed with exit code 1
• pull / test-samsung-quantmodels-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 729ab886adb1d23e3bb62f972e017b8c35348117738d67d2e32b2a0b9fb7c265 /exec failed with exit code 1
• trunk / test-qnn-optimum-model (fp32, focalnet) / linux-job (gh)
  RuntimeError: Command docker exec -t f2cc5d0688eb206c30752686b40a24d94dd18c8a6c81b9bbf6f9095a5afcf25a /exec failed with exit code 1

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / test-qnn-models-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• Test CUDA Builds / test-models-cuda (resnet18) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / android / run-emulator (gh) (#16137)
  Timeout waiting for emulator to boot.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[metascroy]

@larryliu0820 I added a static LLM runner based on the APIs in extension/llm. Can you have a look and give feedback?

[metascroy]

@JacobSzwejbka are you able to review this while Mengwei is out? Or is there a better person?