Skip to content

Only consider ECMA assemblies without DisableRuntimeMarshallingAttribute as having runtime marshalling enabled - #133977

Merged
jkoritzinsky merged 1 commit into
mainfrom
jkoritzinsky-patch-1
Sep 16, 2026
Merged

jkoritzinsky merged 1 commit into
mainfrom
jkoritzinsky-patch-1

Conversation

@jkoritzinsky

Copy link
Copy Markdown
Member

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @dotnet/interop-contrib
See info in area-owners.md if you want to be subscribed.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟡 Changes recommended

Regression coverage for synthetic and ECMA module behavior is still needed.

Get a fresh assessment by requesting another Copilot review.

Review tier: Lite
Findings: 1 Medium severity

Open (1)
What changed in this PR

Updates NativeAOT marshalling detection so only ECMA assemblies without DisableRuntimeMarshallingAttribute are treated as having runtime marshalling enabled.

Changes:

  • Corrects non-ECMA module handling.
  • Prevents false marshalling diagnostics such as IL1005.
File Summary Review comment
src/​coreclr/​tools/​Common/​TypeSystem/​Interop/​IL/​MarshalHelpers.cs Corrects runtime-marshalling detection. Moderate (2 votes): Add regression coverage for synthetic and ECMA modules.

Comment thread src/coreclr/tools/Common/TypeSystem/Interop/IL/MarshalHelpers.cs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants