Arm backend: Add support for custom vela.ini #11958
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
perheld
added
partner: arm
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/11958
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 Cancelled JobAs of commit 78c4c73 with merge base 5335eeb ( CANCELLED JOB - The following job was cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
facebook-github-bot
added
the
CLA Signed
The vela compiler supports the option to specify a custom vela.ini file. But none of the scripts in the arm backend handles this option and forwards it to vela. Previous to this commit this was always hardcoded to "Arm/vela.ini" Now this can be specified with --config that is being forwarded to vela for the following scripts: * examples/arm/run.sh * examples/arm/aot_arm_compiler.py While keeping the default of "Arm/vela.ini" in test/common to not break CI. Change-Id: I5ab25f1784006df96a1e10f97c994024362875da Signed-off-by: [email protected]
perheld
force-pushed
the
upstream/ph-vela.ini-config
branch
from
7c34c38 to
78c4c73
Compare
zingo
approved these changes
Jun 25, 2025
hinriksnaer
pushed a commit
to hinriksnaer/executorch
that referenced
this pull request
Jun 26, 2025
The vela compiler supports the option to specify a custom vela.ini file. But none of the scripts in the arm backend handles this option and forwards it to vela. Previous to this commit this was always hardcoded to "Arm/vela.ini" Now this can be specified with --config that is being forwarded to vela for the following scripts: * examples/arm/run.sh * examples/arm/aot_arm_compiler.py While keeping the default of "Arm/vela.ini" in test/common to not break CI. Signed-off-by: [email protected]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The vela compiler supports the option to specify a custom vela.ini file. But none of the scripts in the arm backend handles this option and forwards it to vela.
Previous to this commit this was always hardcoded to "Arm/vela.ini"
Now this can be specified with --config that is being forwarded to vela for the following scripts:
While keeping the default of "Arm/vela.ini" in test/common to not break CI.
Change-Id: I5ab25f1784006df96a1e10f97c994024362875da
Signed-off-by: [email protected]
cc @digantdesai @freddan80 @per @zingo @oscarandersson8218