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/7.0] [mono][aot] Fixed decompose_flag propagation issues #79855

Merged
merged 1 commit into from
Jan 6, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 20, 2022

Backport of #79849 to release/7.0

It has been reported in 79710 that Mono AOT can fail when compiling an assembly that contains a generic class with a method that returns Type and has a conditional structure.

/cc @jandupej

Customer Impact

This PR fixes the issue and allows successful builds of such assemblies.

Testing

We do not have a CI pipeline for this case. The issue can be replicated by building Mono for Android x64 and trying to compile the example specified in the issue 79710. AOT compilation will fail as described in the issue. AOT compilation will succeed when the fix is applied.

Risk

Low. This PR does not add features, only fixes a basic block flag propagation issue that causes the bug. Very little code is touched.

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

@lambdageek lambdageek added the Servicing-consider Issue for next servicing release review label Dec 20, 2022
@lambdageek lambdageek added this to the 7.0.x milestone Dec 20, 2022
@lambdageek
Copy link
Member

@jandupej please fill in the template and email tactics

@SamMonoRT
Copy link
Member

@jandupej please fill in the template and email tactics

He's validating manually and will update the text, email later. Might not happen till after the holidays, so removing the tags for now

@SamMonoRT SamMonoRT removed the Servicing-consider Issue for next servicing release review label Dec 20, 2022
@SamMonoRT SamMonoRT removed this from the 7.0.x milestone Dec 20, 2022
@carlossanlop
Copy link
Member

@SamMonoRT @jandupej friendly reminder to fill out the template / add servicing-consider label / send email to Tactics.

@jandupej jandupej added the Servicing-consider Issue for next servicing release review label Jan 5, 2023
@jandupej
Copy link
Member

jandupej commented Jan 5, 2023

Build failures are unrelated to this PR.

@SamMonoRT SamMonoRT added this to the 7.0.x milestone Jan 5, 2023
@SamMonoRT
Copy link
Member

Approved via email. Marking as servicing-approved cc @carlossanlop

@SamMonoRT SamMonoRT added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jan 6, 2023
@carlossanlop carlossanlop modified the milestones: 7.0.x, 7.0.3 Jan 6, 2023
@carlossanlop
Copy link
Member

Thanks for the ping, @SamMonoRT

Approved by Tactics (7.0.3).
Signed off by area owners.
No OOB changes required for this change (native code).
CI failures are unrelated: #75018 and #79097, plus some cancellations.
Ready to merge. :shipit:

@carlossanlop carlossanlop merged commit e516d18 into release/7.0 Jan 6, 2023
@carlossanlop carlossanlop deleted the backport/pr-79849-to-release/7.0 branch January 6, 2023 17:27
@ghost ghost locked as resolved and limited conversation to collaborators Feb 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-VM-meta-mono Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants