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

      Test output contained the following extra linker warnings:
      + ILLink : Trim analysis warning IL2065: System.Reflection.Emit.TypeBuilderImpl.CheckInterfaces(Type[]): Value passed to implicit 'this' parameter of method 'System.Type.GetMethods(BindingFlags)' can not be statically determined and may not meet 'DynamicallyAccessedMembersAttribute' requirements. [C:\h\w\9F8E08D0\t\dotnetSdkTests\xt13z3tr.2qv\ILLink_verify---A58CFA90\AnalysisWarningsOnHelloWorldApp\AnalysisWarningsOnHelloWorldApp.csproj]
      + ILLink : Trim analysis warning IL2065: System.Reflection.Emit.TypeBuilderImpl.CheckInterfaces(Type[]): Value passed to implicit 'this' parameter of method 'System.Type.GetInterfaces()' can not be statically determined and may not meet 'DynamicallyAccessedMembersAttribute' requirements. [C:\h\w\9F8E08D0\t\dotnetSdkTests\xt13z3tr.2qv\ILLink_verify---A58CFA90\AnalysisWarningsOnHelloWorldApp\AnalysisWarningsOnHelloWorldApp.csproj]

@buyaa-n the CheckInterfaces method looks like it will block things unnecessarily when default interface methods are involved and it will not block enough things when unimplemented static abstracts are involved.

I don't actually understand why we're not seeing this in this repo and only in the SDK repo.

Perhaps the live build of linker is not used consistently in the runtime repo? Linker failures in #95980 suggest that be the case. Some issues are promptly discovered when changing llinker code in runtime repo during the initial PR, some are discovered passively when SDK is updating runtime (few times a day) and the rest are discovered at very low pace when runtime is updating SDK (few times a year).

I don't actually understand why we're not seeing this in this repo and only in the SDK repo.

dotnet/runtime suppresses IL2065. I think those suppressions were supposed to be removed as part of #38033 and should be cleaned up.