Linker overhaul#1
Draft
Vigintillionn wants to merge 24 commits into
Draft
Conversation
…byte bug and add support for .equ/.equiv/.set/... directives
…ols and li, rd, SYMBOL not properly lowering
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
1 participant
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.
Rewrite the linker to be cleaner, allow support for
.equwith expressions, for custom sections and for linking multiple files. Goal is to be GAS compliant..includepreprocessing layerCurrent limitations:
%hi/%lo/%pcrel_*relocation syntax.equ/.space/.alignand.-in-those-contexts cannot reference forward symbols.equevaluated during the walk that references a.bsslabel captures its pre-shift (relative) offsetli rd, SYMBOLwith a value that needslui+addiis still a singleaddi