Core: Correct branch analysis truncation #14027
Merged
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.
#14017 broke these functions, by truncating the signed offset to 16 bits (discarding the two most significant bits.) Only matters for larger branch jumps, but I don't want the debugger / function scanning / stack walk to get confused.
For clarity, just to explain since #14017 got merged:
In contrast:
Which could result in values becoming incorrectly unsigned or signed after the truncation, as well as reducing the magnitude incorrectly.
-[Unknown]