-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
<format> use _MSVC_EXECUTION_CHARACTER_SET #2493
Merged
StephanTLavavej
merged 10 commits into
microsoft:main
from
barcharcraz:format_msvc_execution_character_set
Feb 1, 2022
Merged
<format> use _MSVC_EXECUTION_CHARACTER_SET #2493
StephanTLavavej
merged 10 commits into
microsoft:main
from
barcharcraz:format_msvc_execution_character_set
Feb 1, 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
For clang use ____clang_literal_encoding__, clang 14 will learn _MSVC_EXECUTION_CHARACTER_SET, but ____clang_literal_encoding__ is in clang 13. Additionally for the "slow path" get the "format codepage" using these new macros (at compile-time) rather than assuming the active codepage is the same as the execution character set.
This comment has been minimized.
This comment has been minimized.
jovibor
reviewed
Jan 20, 2022
Remember to actually write code that compiles under clang :/
StephanTLavavej
requested changes
Jan 28, 2022
StephanTLavavej
approved these changes
Jan 28, 2022
CaseyCarter
requested changes
Jan 28, 2022
StephanTLavavej
approved these changes
Jan 29, 2022
CaseyCarter
approved these changes
Jan 29, 2022
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Thanks for this significant performance improvement! 🚀 🚀 😸 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This should drastically increase format's performance in the "default" case (still need to rerun my toy benchmarks though)
For clang use __clang_literal_encoding, clang 14 will learn
_MSVC_EXECUTION_CHARACTER_SET, but __clang_literal_encoding
is in clang 13.
Additionally for the "slow path" get the "format codepage" using
these new macros (at compile-time) rather than assuming the
active codepage is the same as the execution character set.
ABI Impact:
This changes which versions of some templates get used, and could cause ODR violations, but in general should make people's ABI situation better rather than worse.
In particular windows 1251 will now use the "fast path" on msvc, so if you link clang code (which always used the fast path) to
non-clang code you no longer have an ODR violation in std::foramt (although your codepages differ, so there are probably still relatively benign ODR violations elsewhere).
fixes: #2342