Skip to content

Conversation

@AaronRobinsonMSFT
Copy link
Member

@ghost
Copy link

ghost commented Mar 5, 2021

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

Issue Details

Fixes #42767

/cc @GrabYourPitchforks

Author: AaronRobinsonMSFT
Assignees: -
Labels:

area-Infrastructure

Milestone: 6.0.0

@AaronRobinsonMSFT
Copy link
Member Author

@GrabYourPitchforks I've not added the compiler flags from the issues to this PR. I added them locally and compiled across x86/Amd64/ARM/ARM64 and Debug/Release on Windows.

Do you have a place in mind where those flags should be added?

Revert usage of _vsnwprintf_s since it has different semantics than
  _vsnwprintf. Verified _vsnwprintf is being used correctly.
@AaronRobinsonMSFT AaronRobinsonMSFT merged commit 3df7a6e into dotnet:main Mar 19, 2021
@AaronRobinsonMSFT AaronRobinsonMSFT deleted the runtime42767 branch March 19, 2021 03:58
AaronRobinsonMSFT added a commit to AaronRobinsonMSFT/zlib that referenced this pull request Mar 19, 2021
During some CA work in the dotnet runtime project we discovered the VC++ code analysis has trouble determining the follow value is properly initialized prior to use. Instead of adding a suppression it seemed easier to simply initialize it.

See dotnet/runtime#49194 (comment) for context.
@ghost ghost locked as resolved and limited conversation to collaborators Apr 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tracking issue: enable more MSVC warnings

4 participants