Add coreml_compute_plan.py: report which CoreML ops dispatch to ANE / GPU / CPU

[john-rocky]

Summary

CoreML decides at compile/load time which device each MIL operation will
execute on, and coremltools 9.0+ exposes that through MLComputePlan.
The recurring question on the issue tracker is "why isn't my model
running fully on the ANE?" — for example:

• llama model is not fully lowered to ANE (coreml backend) #4091 — llama model is not fully lowered to ANE
• CoreML model is crashing on iPhone GPU, but not on iPhone CPU or macOS GPU #11541 — CoreML model is crashing on iPhone GPU, but not on iPhone CPU or macOS GPU
• ANE compile OOMs on certain input shapes #8439 — ANE compile OOMs on certain input shapes
• CPU Overhead After ANE Execution #8445 — CPU Overhead After ANE Execution

Today the only way for an ExecuTorch user to answer it is to break out
Swift / Xcode. This PR adds a Python wrapper around MLComputePlan so
the answer is one shell command:

$ python coreml_compute_plan.py --model_path my_model.mlpackage \
      --compute_units cpu_and_ne --show_non_ane

=== my_model.mlpackage ===
  ANE:   412 / 480 ( 85.8%)
  CPU:    68 / 480 ( 14.2%)

  Non-ANE op types:
       32  ios17.cast
       18  ios17.gather
       12  ios17.reshape
        6  ios17.constexpr_blockwise_shift_scale

Inputs supported:

Input	Behavior
.pte	Extract every Core ML partition into a tempdir, then analyze each.
.mlpackage	Compile to .mlmodelc in a tempdir, then analyze.
.mlmodelc	Analyze directly.

The PTE path reuses the same JSON/named-data extraction logic that
extract_coreml_models.py uses, and is inlined into the script so it can
be run against a plain CoreML model without depending on the executorch
package.

Test plan

Added test_coreml_compute_plan.py covering:

• _device_name(...) for None and a stub MLNeuralEngineComputeDevice.
• _COMPUTE_UNIT_CHOICES mapping (cpu_and_ne / all).
• analyze_one(...) end-to-end on a tiny relu(x @ x.T) + x.sum()
  mlpackage built with coremltools.convert(...): returns rows for
  every dispatched op, with a main function and the expected MIL op
  types (matmul, relu, add, reduce_sum).

$ python -m pytest examples/apple/coreml/scripts/test_coreml_compute_plan.py -v
============================== 7 passed in 3.68s ===============================

I also ran the script against a few hand-built .mlpackage and
.mlmodelc files on macOS 26 with coremltools 9.0 and verified the
output matches what MLComputePlan returns directly.

Authored with Claude.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

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.