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/8.0] Fix runtime dispatch to static virtuals on interface types #91440

Merged
merged 1 commit into from
Sep 1, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 1, 2023

Backport of #91374 to release/8.0

/cc @MichalStrehovsky

Customer Impact

This was a customer reported issue at #90333.

It's not possible to resolve certain static virtual interface dispatches at runtime.

Most static virtual interface dispatches get resolved at compile time. But for some forms of dynamic code, we need to be able to compute this at runtime. Logic was missing to do that on interfaces.

Testing

All Native AOT testing, plus targeted tests, plus customer repro.

Risk

Low. We have decent test coverage.

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

We were not generating information about static virtuals on interface types. Information about default interface methods normally goes to the class, but if the T we're dispatching on is an interface, this information wasn't generated. The fix is to put this information into dispatch maps and sealed vtables, same way we do for classes.

The test shows what the problem is - if we change `IBar` to be a class, things would work even before this PR.
@ghost
Copy link

ghost commented Sep 1, 2023

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #91374 to release/8.0

/cc @MichalStrehovsky

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author: github-actions[bot]
Assignees: -
Labels:

area-NativeAOT-coreclr

Milestone: -

Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved. once ready this can be merged

@jeffschwMSFT jeffschwMSFT added the Servicing-approved Approved for servicing release label Sep 1, 2023
@jeffschwMSFT jeffschwMSFT added this to the 8.0.0 milestone Sep 1, 2023
@carlossanlop carlossanlop merged commit 2134e62 into release/8.0 Sep 1, 2023
119 of 121 checks passed
@carlossanlop carlossanlop deleted the backport/pr-91374-to-release/8.0 branch September 1, 2023 18:34
@radical radical mentioned this pull request Sep 26, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Oct 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-NativeAOT-coreclr Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants