Update attributes.md likely/unlikely attribute optimization limitation #3855
Conversation
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
We had 2 feedback bugs for likely/unlikely where customers commented about block reordering optimization not happening when they specify these attributes. As per the request of one of the feedback tickets, adding a specific note about this optimization not being implemented yet in the compier. https://developercommunity.visualstudio.com/t/Gy-changes-C20-branch-hint-optimiza/10023042#T-ND10024186 https://developercommunity.visualstudio.com/t/likely--unlikely-should-avoid-c/1603545
Contributor
|
@prjoseph : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
@corob-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
colin-home
approved these changes
Apr 27, 2022
Contributor
|
@prjoseph Thanks for the update. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
We had 2 feedback bugs for likely/unlikely where customers commented about block reordering optimization not happening when they specify these attributes.
As per the request of one of the feedback tickets, adding a specific note about this optimization not being implemented yet in the compier.
https://developercommunity.visualstudio.com/t/Gy-changes-C20-branch-hint-optimiza/10023042#T-ND10024186
https://developercommunity.visualstudio.com/t/likely--unlikely-should-avoid-c/1603545