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

Don't probe for A/W variants of entry points on non-Windows. #33250

Merged
merged 4 commits into from
Mar 11, 2020

Conversation

jkoritzinsky
Copy link
Member

Fixes #33246 for CoreCLR

@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't add an area label to this PR.

Checkout this page to find out which area owner to ping, or please add exactly one area label to help train me in the future.

Copy link
Member

@stephentoub stephentoub left a comment

Choose a reason for hiding this comment

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

Should we add any tests to validate expected behavior?

@jkotas jkotas added the breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. label Mar 5, 2020
@AaronRobinsonMSFT
Copy link
Member

@stephentoub I agree. Anytime we add the 'breaking-change' tag some level of testing should be a requirement.

@jkoritzinsky
Copy link
Member Author

I've updated the ExactSpelling tests to test the new behavior.

@jkotas jkotas merged commit a6fcb15 into dotnet:master Mar 11, 2020
@jkoritzinsky jkoritzinsky deleted the aw-windows-only branch March 11, 2020 04:42
@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Interop-coreclr breaking-change Issue or PR that represents a breaking API or functional change over a prerelease.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove A/W probing for PInvokes on non-Windows platforms
5 participants