-
Notifications
You must be signed in to change notification settings - Fork 742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perf: Apply various workarounds to mitigate PG-AOT dotnet/runtime issue #56309 #7005
Conversation
These changes are required to reduce the interpreter performance hit. The AOT compiler detects try/catch/finally containing methods and forces the interpreter, even if the try/catch is not in the execution path. Inner methods are created to reduce the size of the interpreter-executed code, and return to AOT as soon as possible.
68bd3b7
to
5cbbec2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TL;JA
@carldebilly does this mean: Too long J'ai approved? |
Too Long; Just Approved ;-) |
The build 33134 found UI Test snapshots differences: Details
|
See #7005 for additional details
See #7005 for additional details
See #7005 for additional details
See unoplatform#7005 for additional details
See unoplatform#7005 for additional details
GitHub Issue (If applicable): dotnet/runtime#56309
PR Type
What kind of change does this PR introduce?
What is the new behavior?
These changes are required to reduce the interpreter performance hit. The AOT compiler detects try/catch/finally containing methods and forces the interpreter, even if the try/catch is not in the execution path.
Inner methods are created to reduce the size of the interpreter-executed code, and return to AOT as soon as possible.
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.Other information
Internal Issue (If applicable):