| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Method compilation was continuing and we ended up failing with invalid IL.
…ption throw In the final stages of method compilation, when trying to compute clause ranges, we were asserting because the clause bblocks haven't been reached for compilation.
|
Tagging subscribers to this area: @steveisok, @vitek-karas |
Sorry, something went wrong.
|
@BrzVlad please take a look at the PR failures and merge when ready |
Sorry, something went wrong.
|
needs a review for merging |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM!
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Backport of #110078 to release/9.0-staging
Customer Impact
AOT of some assemblies can lead to compilation crashes, on iOS for example. This would force users to use interpreter instead.
Regression
Yes.
Testing
Tested with sample application provided by customer.
Risk
Low. In rare cases, when typeload exception was detected during compile time, we were emitting code to throw this exception at runtime (this was behavior introduced in net9). This functionality had bugs leading to crashes instead during compilation. This PR has impact only on those scenarios that were already crashing.