Skip to content

Arm backend: Generate ETRecord from arm_aot_compiler #13273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

zingo
Copy link
Collaborator

@zingo zingo commented Aug 11, 2025

An ETRecord file is generated if ETDump or BundleIO is used. This also adds tests for --bundleio and --etdump to make sure it works.

cc @digantdesai @freddan80 @per @oscarandersson8218

An ETRecord file is generated if ETDump or BundleIO is used.
This also adds tests for --bundleio and --etdump to make sure
it works.

Signed-off-by: Zingo Andersen <[email protected]>
Change-Id: If4e1fabba207905eaea1e8381e4d23476512c33b
@zingo zingo requested a review from digantdesai as a code owner August 11, 2025 11:38
@zingo zingo added partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm ciflow/trunk release notes: devtools Changes to dev tooling, for example the debugger & profiler release notes: arm Changes to the ARM backend delegate labels Aug 11, 2025
Copy link

pytorch-bot bot commented Aug 11, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure, 1 Unrelated Failure

As of commit 8f569e5 with merge base 72580d2 (image):

NEW FAILURE - The following job has failed:

BROKEN TRUNK - The following job 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 Aug 11, 2025
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. partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm release notes: arm Changes to the ARM backend delegate release notes: devtools Changes to dev tooling, for example the debugger & profiler
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant