Fix IR operation usage to use OpSize when possible #4132
+657
−656
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
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.
No functional change.
This is a continued stride towards using OpSize enums instead of constant numbers to reduce confusion and misunderstandings.
It gets very confusing at times when an argument to an IR operation is a size versus an index, or scale or another constant. We had already cleaned up a decent amount of this early this year, late last year but this hits all the OpcodeDispatcher files in the folder. Currently skips the base file, but once that one is done then we can mop up the rest of the IR operations to remove implicit size conversion.
Just a little cleanup while I'm distracted.