Skip to content
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

Conversation

fanyang-mono
Copy link
Member

@fanyang-mono fanyang-mono commented Aug 31, 2023

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.

@dotnet-issue-labeler 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
@fanyang-mono fanyang-mono added this to the 6.0.x milestone Aug 31, 2023
@ghost ghost assigned fanyang-mono Aug 31, 2023
@fanyang-mono 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 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
@fanyang-mono
Copy link
Member Author

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@carlossanlop
Copy link
Member

carlossanlop commented Aug 31, 2023

@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

@fanyang-mono
Copy link
Member Author

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@fanyang-mono
Copy link
Member Author

fanyang-mono commented Sep 5, 2023

Approved via Tactics Email.

@fanyang-mono fanyang-mono added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Sep 5, 2023
@fanyang-mono fanyang-mono merged commit b9895c9 into dotnet:release/6.0-staging Sep 5, 2023
@ghost 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.
Labels
area-Interop-mono Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants