-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[release/7.0] [mono][wasm] Disable AOTing methods which contain catch clauses insid… #78732
Conversation
…e finally/filter clauses. When the ENDFINALLY opcode of the outer clause is encountered while executing the inner catch clause from run_with_il_state (), it will assert since it doesn't know where to continue execution.
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Failures are unrelated. |
@vargaz if this is ready, please send the email to Tactics requesting approval. For the January release, we will only have a window of one day to merge backports (Nov. 29-30), so I'm asking all backport submitters to get their PRs ready for me to just hit merge on that day. |
Sent |
Approved by tactics. |
Branding has been done. Milestone is 7.0.2. Signed-off by area owners. Approved by Tactics. No OOB package authoring changes needed. CI failure is unrelated (#78778). |
Backport of #78653 to release/7.0
/cc @vargaz
Customer Impact
Fixes #78358 which is a regression
on wasm in AOT mode caused by #77059.
The regression was not detected because not all wasm tests are ran on the backport PRs.
Testing
CI with /azp run runtime-wasm
Risk
Low, only affects wasm in AOT mode, fixes a regression.