JIT: Unprotect handler entry after finally removal #115907
Merged
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:
fgRemoveEmptyTry
will remove theBBF_DONT_REMOVE
guard 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.