Skip to content

Arm backend: Allow Arm executor_runner CMake to run standalone#19018

Draft
usamahz wants to merge 1 commit intopytorch:mainfrom
usamahz:feature/standalone-runner
Draft

Arm backend: Allow Arm executor_runner CMake to run standalone#19018
usamahz wants to merge 1 commit intopytorch:mainfrom
usamahz:feature/standalone-runner

Conversation

@usamahz
Copy link
Copy Markdown
Collaborator

@usamahz usamahz commented Apr 21, 2026

Summary

  1. Arm backend: Allow Arm executor_runner CMake to run
    standalone
  2. Arm backend: Manage Arm Ethos-U SDK setup and PTE
    inputs
  3. Arm backend: Hook selective build into the standalone
    runner
  4. Arm backend: Make Arm bare-metal install/export
    subproject friendly
  5. Arm backend: Keep bare-metal install artifacts for
    runner reuse
  6. Arm backend: Expand run.sh CLI knobs for bare-metal
    builds
  7. Arm backend: Auto-configure Arm backend runner builds
    via presets
  8. Arm backend: Document the new Arm runner workflow

Testing

  • executor_runner CI (Ethos-U55/U85/VGF flows)

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @Sebastian-Larsson @robell

- Detect standalone invocation, derive EXECUTORCH_ROOT, and expose
  ARM_EXECUTOR_RUNNER_STANDALONE for diagnostics.
- Load ExecuTorch presets and add_subdirectory(EXECUTORCH_ROOT ...) when
  building out of tree.
- Refresh pte_to_header.py with a shebang and updated Arm copyright.

Change-Id: I4582326c72a0b571c495aca64b2c58e45bfbb5be
Signed-off-by: Usamah Zaheer <usamah.zaheer@arm.com>
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Apr 21, 2026

🔗 Helpful Links

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

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

❌ 1 Cancelled Job, 5 Unrelated Failures

As of commit 10dc5c9 with merge base ccaf17e (image):

CANCELLED JOB - The following job was cancelled. Please retry:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 21, 2026
@github-actions github-actions Bot added ciflow/trunk module: arm Issues related to arm backend labels Apr 21, 2026
@github-actions
Copy link
Copy Markdown

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.

@usamahz usamahz marked this pull request as draft April 21, 2026 12:31
@usamahz
Copy link
Copy Markdown
Collaborator Author

usamahz commented Apr 21, 2026

I will merge after all 8 commits land in this PR - so until then please do not merge! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. module: arm Issues related to arm backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant