Avoid calling memcpy in swap#5500
Merged
StephanTLavavej merged 8 commits intomicrosoft:mainfrom May 17, 2025
Merged
Conversation
StephanTLavavej
approved these changes
May 15, 2025
Member
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Member
🔁 💱 🐱 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #5481
The release codegen is the same, the benchmark results are the same.
memcpycalls are now not emitted in any mode. In/Odwe haverep movsb, which is pretty good for a debug mode.unsigned charis kept for underlying type as it doesn't have alignment requirements, and also is a valid alias for any object.@frederick-vs-ja pointed out that the strict aliasing rule is still violated here.
I excluded Clang (and thus Intel), I verified Clang already optimizes the usual swap loop on its own.MSVC doesn't take advantage of strict aliasing, so it is fine 🔥🐶☕🔥