[SOL] Fix ALU32 instructions with explicit sign extension #116
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
dmakarov
approved these changes
Dec 6, 2024
LucasSte
merged commit f082558
into
anza-xyz:solana-rustc/18.1-2024-05-19
17 checks passed
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.
ALU32 instructions couldn't be correctly used because the SBF virtual machine lacks the JMP32 instruction class. Consequently, the compiler must adjust registers (sign or zero extend them) before using the existing JMP instruction class.
#114 introduced the explicit sign extension instruction, and it allowed us to properly fix that. This PR makes the ALU32 instructions usable.