-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Remove "wprintf" from PAL #77852
Merged
AaronRobinsonMSFT
merged 4 commits into
dotnet:main
from
AaronRobinsonMSFT:remove_wprint_from_pal
Nov 4, 2022
Merged
Remove "wprintf" from PAL #77852
AaronRobinsonMSFT
merged 4 commits into
dotnet:main
from
AaronRobinsonMSFT:remove_wprint_from_pal
Nov 4, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The last usage was in FormatMessageW, which only used wprintf syntax for messages that used embeded printf format between two "!". We do not use this feature in any of our messages so this code path is technically unused.
_woutput_s was not removed because it is intertwined with the implementation for printf. The linker will just prune the implementation anyways. Remove all wprintf testing from PAL
am11
approved these changes
Nov 3, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! 👍
FormatMessageW errors if embedded formating is used Update PAL tests for FormatMessageW
janvorli
approved these changes
Nov 4, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
This was referenced Nov 4, 2022
Issues are known and properly tagged above. |
radical
added a commit
to radical/runtime
that referenced
this pull request
Nov 4, 2022
This completely broke `dotnet-runtime-perf` pipeline for wasm runs. This reverts commit 8036885. Issue: dotnet#77883
ghost
locked as resolved and limited conversation to collaborators
Dec 4, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The last usage was in
FormatMessageW
, whichonly used wprintf syntax for messages that used
embedded printf format between two "!". We do
not use this feature in any of our messages so
this code path is technically unused.
Remove
_snwprintf_s
from PALRemove
_vsnwprintf_s
from PAL_woutput_s
was not removed because it is intertwinedwith the implementation for printf. The linker will just
prune the implementation anyways.
Remove all wprintf testing from PAL