[release/9.0-staging] JIT: Include more edges in BlockDominancePreds
to avoid a JIT crash
#110568
+86
−35
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.
Backport of #110531 to release/9.0-staging
/cc @jakobbotsch
Customer Impact
Certain patterns of exception handling (involving nested filters, try-finally and try-catch) can cause the JIT to crash when the method is jitted with optimizations enabled. Reported by customer in #109981.
The problem occurs when:
See the added test case for a C# example.
In this case the JIT computes a wrong dominator block for the catch-handler (2), which later causes a null pointer dereference.
Regression
The issue was introduced in #94672.
Testing
Added a test case that hits the crash without the fix. Also verified the fix on the customer's test case.
Risk
Low.