fix: Clear opcode and immediate fields before rewriting MOVZ/MOVN relocations in AArch64 - #1794
Merged
Merged
Conversation
davidlattimore
approved these changes
Apr 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
2 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.
context: #1791 (comment)
The
Movnzvariant ofwrite_to_value()selects between MOVZ (bit 30 = 1) and MOVN (bit 30 = 0) at link time depending on the sign of the resolved value. Since it used onlyor_from_slice(), bit 30 could never be cleared, so a MOVZ placeholder in the object file could not be rewritten to MOVN. The immediate field was also corrupted by leftover bits.