Link-time constants in relocs.txt#52
Merged
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
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.
Renamed linker variables to link-time constants. They're not really variables, they're as constant as a
constin C/C++, so that's why I renamed them :POther than that, this PR mainly adds support for using link-time constants in relocs.txt.
Example usage:
kind:link_time_const(__DTCM_LO)The
toandmoduleattributes are optional for link-time constants. They also have no effect on such relocations and will be removed bydsd format. The same is now also true for themoduleattribute for overlay ID relocations.