Arm backend: Decompose sub/add with alpha!=1#14939
Merged
GregoryComer merged 1 commit intorelease/1.0from Oct 9, 2025
Merged
Conversation
This was previously not supported, causing crashes in quantization, and incorrect output in floating point. Signed-off-by: Erik Lundell <erik.lundell@arm.com> (cherry picked from commit dda2705)
This was referenced Oct 9, 2025
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14939
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 Cancelled JobsAs of commit a07cc3e with merge base e0dda90 ( CANCELLED JOBS - The following jobs were cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
GregoryComer
approved these changes
Oct 9, 2025
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
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.
This was previously not supported, causing crashes in quantization, and incorrect output in floating point.
cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai