-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[release/6.0-staging] [Mono] Fix offset calculation for nested struct, when pinvoke is enabled #91424
Merged
fanyang-mono
merged 2 commits into
dotnet:release/6.0-staging
from
fanyang-mono:backport_91292_to_6
Sep 5, 2023
Merged
[release/6.0-staging] [Mono] Fix offset calculation for nested struct, when pinvoke is enabled #91424
fanyang-mono
merged 2 commits into
dotnet:release/6.0-staging
from
fanyang-mono:backport_91292_to_6
Sep 5, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fanyang-mono
requested review from
vargaz,
lambdageek and
SamMonoRT
as code owners
August 31, 2023 20:54
dotnet-issue-labeler
bot
added
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Aug 31, 2023
ghost
assigned fanyang-mono
Aug 31, 2023
fanyang-mono
added
area-Codegen-JIT-mono
area-Codegen-AOT-mono
area-Interop-mono
Servicing-consider
Issue for next servicing release review
and removed
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
labels
Aug 31, 2023
fanyang-mono
changed the title
[release/7.0-staging] [Mono] Fix offset calculation for nested struct, when pinvoke is enabled
[release/6.0-staging] [Mono] Fix offset calculation for nested struct, when pinvoke is enabled
Aug 31, 2023
/azp run runtime-extra-platforms |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
@fanyang-mono if this is ready, can you please request a code review sign-off and also send an email to Tactics requesting approval? Also, do you see any CI failures related to this change? September 10th is the code complete date for the October Release. cc @SamMonoRT |
lambdageek
approved these changes
Sep 1, 2023
SamMonoRT
approved these changes
Sep 1, 2023
/azp run runtime-extra-platforms |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Approved via Tactics Email. |
fanyang-mono
added
Servicing-approved
Approved for servicing release
and removed
Servicing-consider
Issue for next servicing release review
labels
Sep 5, 2023
ghost
locked as resolved and limited conversation to collaborators
Oct 5, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #91292 to release/6.0-staging
/cc @fanyang-mono
Customer Impact
Prior to this change, the offset of fields was calculated incorrectly for nested struct when PInvoke is enabled. One of the Android customers hit an assertion when build an app.
Testing
Added a new test, which passed on CI.
Validated customer's use case locally. It works correctly now.
Risk
Low risk.