Conversation
nagisa
approved these changes
Mar 4, 2026
Contributor
nagisa
left a comment
nagisa
left a comment
There was a problem hiding this comment.
I am generally wary of likely/unlikely cause while they could be doing good in a particular release, they can easily inhibit an optimization in the next. Its a long-standing and well known issue with these intrinsics.
But that wariness is pretty inactionable so :stamp:
joncinque
approved these changes
Mar 4, 2026
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.
Problem
The upcoming platform-tools update comes with Rust
1.89.0. The compiler in that version seems to require more hints to optimize the "hot" path in a few instructions.Solution
Use
likely/unlikelycompiler hints in a few more places.cc: @LucasSte @nagisa