JIT: Unprotect handler entry after finally removal#115907
Merged
amanasifkhalid merged 1 commit intodotnet:mainfrom May 22, 2025
Merged
JIT: Unprotect handler entry after finally removal#115907amanasifkhalid merged 1 commit intodotnet:mainfrom
amanasifkhalid merged 1 commit intodotnet:mainfrom
Conversation
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR ensures that the handler entry block loses its BBF_DONT_REMOVE guard when an empty try is removed, and it cleans up duplicate flag removals in the cloned finally logic.
- Unprotect handler entry block in
fgRemoveEmptyTry - Consolidate
BBF_DONT_REMOVEremovals infgCloneFinally
Contributor
Author
|
@dotnet/jit-contrib PTAL. Small diffs. Thanks! |
AndyAyersMS
approved these changes
May 22, 2025
Contributor
Author
|
/ba-g android build stuck |
Open
3 tasks
SimaTian
pushed a commit
that referenced
this pull request
May 27, 2025
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.
Found while working on #115850. Suppose we have the following flowgraph:
fgRemoveEmptyTrywill remove theBBF_DONT_REMOVEguard from the try entry if it decides to remove the region, but it won't do so for the corresponding finally entry:If we remove the guard for the finally entry in this case, loop inversion will make it unreachable, and flow opts will remove it entirely, rather than converting it into an unnecessary
BBJ_THROW. This change enables that.