Fix callNative.S clang error for linux/aarch64#4
Merged
guillerodriguez merged 1 commit intomasterfrom Feb 3, 2026
Merged
Conversation
The instruction 'sub sp, sp, w3' is invalid because sp is 64-bit
but w3 is 32-bit. GCC/GAS accepts this (and implicitly adds the
uxtw extend specifier), but clang rejects it:
error: too few operands for instruction
sub sp, sp, w3
^~~~~~~~~~~~~~
Fix this by making the zero-extend explicit, which works under
both toolchains.
Signed-off-by: Guillermo Rodríguez <grodriguez@ingelabs.com>
f9cb701 to
59c7153
Compare
avazquezdev
approved these changes
Feb 3, 2026
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
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 instruction 'sub sp, sp, w3' is invalid because sp is 64-bit but w3 is 32-bit. GCC/GAS accepts this (and implicitly adds the uxtw extend specifier), but clang rejects it:
error: too few operands for instruction
sub sp, sp, w3
^~~~~~~~~~~~~~
Fix this by making the zero-extend explicit, which works under both toolchains.