Make the renaming of reserved registers configurable #50
Conversation
This file contains 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
This commit introduces the config option `reserved_regs_are_locked`. When set (default), it means that reserved registers are treated as locked, that is, existing uses will not be renamed. When unset, existing used of reserved registers may (in fact, will) be renamed.
hanno-becker
force-pushed
the
reserved_locked_regs
branch
from
92f84f1 to
4008b92
Compare
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.
This PR introduces the config option
reserved_regs_are_locked. When set (default), it means that reserved registers are treated as locked, that is, existing uses will not be renamed. When unset, existing used of reserved registers may (in fact, will) be renamed.More details in
config.py.Fixes: #49