[clr-interp] ret instructions are unconditional branches in control flow#120757
Merged
davidwrighton merged 1 commit intoOct 15, 2025
Merged
Conversation
…n that they do not link to the next block
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR fixes control flow handling for return instructions in the CoreCLR interpreter by treating them as unconditional branches that don't link to subsequent blocks.
- Ensures
retinstructions don't incorrectly link to the next basic block - Adds
linkBBlocks = falseafter bothleaveandretinstruction handling
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
ret instructions are similar to unconditional branches in that they do not link to the next block