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

Move System.Net.Http ILLink suppressions to LibraryBuild. #50053

Merged
merged 1 commit into from
Mar 23, 2021

Conversation

eerhardt
Copy link
Member

This suppression is necessary because we don't have access to the Xamarin and Mono libraries that are used by System.Net.Http.

Contributes to #45623

Follow up from #47083 (comment).

This suppression is necessary because we don't have access to the Xamarin and Mono libraries that are used by System.Net.Http.

Contributes to dotnet#45623
@ghost
Copy link

ghost commented Mar 22, 2021

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

Issue Details

This suppression is necessary because we don't have access to the Xamarin and Mono libraries that are used by System.Net.Http.

Contributes to #45623

Follow up from #47083 (comment).

Author: eerhardt
Assignees: -
Labels:

area-System.Net.Http

Milestone: -

@eerhardt eerhardt added the linkable-framework Issues associated with delivering a linker friendly framework label Mar 22, 2021
@ghost
Copy link

ghost commented Mar 22, 2021

Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @tannergooding, @sbomer
See info in area-owners.md if you want to be subscribed.

Issue Details

This suppression is necessary because we don't have access to the Xamarin and Mono libraries that are used by System.Net.Http.

Contributes to #45623

Follow up from #47083 (comment).

Author: eerhardt
Assignees: -
Labels:

area-System.Net.Http, linkable-framework

Milestone: -

@eerhardt
Copy link
Member Author

Libraries Test Run release coreclr windows x86 Debug failed is #48851

runtime (Installer Build and Test coreclr windows_x86 Debug) is an infrastructure issue.

@@ -73,6 +74,8 @@
Include="$(ILLinkSuppressionsXmlFile)" />
<ILLinkSuppressionsXmls Condition="Exists('$(ILLinkSuppressionsConfigurationSpecificXmlFile)')"
Include="$(ILLinkSuppressionsConfigurationSpecificXmlFile)" />
<ILLinkSuppressionsXmls Condition="Exists('$(ILLinkSuppressionsLibraryBuildXmlFile)')"
Copy link
Member

Choose a reason for hiding this comment

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

Will this collide with libraries which already define a LibraryBuild.xml?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure what you mean. No other libraries already define a LibraryBuild.xml. Just CoreLib, but all CoreLib ILLink files are handled specially because it doesn't get binplaced.

Copy link
Member

Choose a reason for hiding this comment

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

This is what I meant:

C:\Users\joperezr\git\runtime>dir /s /b *LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\coreclr\System.Private.CoreLib\src\ILLink\ILLink.Suppressions.LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\libraries\System.ComponentModel.TypeConverter\src\ILLink\ILLinkTrim_LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\libraries\System.Diagnostics.StackTrace\src\ILLink\ILLinkTrim_LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\libraries\System.Private.CoreLib\src\ILLink\ILLink.Suppressions.LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\libraries\System.Private.CoreLib\src\ILLink\ILLinkTrim_LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\libraries\System.Private.Xml\src\ILLink\ILLinkTrim_LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\libraries\System.Private.Xml.Linq\src\ILLink\ILLinkTrim_LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\libraries\System.Security.Claims\src\ILLink\ILLinkTrim_LibraryBuild.xml
C:\Users\joperezr\git\runtime\src\libraries\System.Security.Principal.Windows\src\ILLink\ILLinkTrim_LibraryBuild.xml

So corelib is one, but I found others that had a LibraryBuild as well. That said, seems like I was getting confused as those doesn't seem to be suppressions, but instead just the old Linker files that would just preserve types/members.

Copy link
Member Author

Choose a reason for hiding this comment

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

ILLink.Suppressions.LibraryBuild.xml is not the same as ILLinkTrim_LibraryBuild.xml. The Suppressions file suppresses ILLink warnings. The ILLinkTrim files tell the linker what to preserve unconditionally. The LibraryBuild part of each means the same thing though - "this file is only used during the build of the library, not in the user's application".

I've been meaning to rename the old name ILLinkTrim.xml to ILLink.Descriptors.xml (and subsequently the _LibraryBuild.xml files.) See #37651. This confusion gives me enough reasoning to do it now, I've been putting it off since 5.0.

Copy link
Member

@joperezr joperezr left a comment

Choose a reason for hiding this comment

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

Other than the one question this LGTM

@eerhardt eerhardt merged commit 3a144a2 into dotnet:main Mar 23, 2021
@eerhardt eerhardt deleted the HttpILLinkWarnings branch March 23, 2021 02:34
@ghost ghost locked as resolved and limited conversation to collaborators Apr 23, 2021
@karelz karelz added this to the 6.0.0 milestone May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Http linkable-framework Issues associated with delivering a linker friendly framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants