Don't ask for pointers to have the fill of their contents.#2129
Merged
Don't ask for pointers to have the fill of their contents.#2129
Conversation
When we're doing, say, a `sgt` comparison on a memory address, we shouldn't make the _pointer_ be signed: the signedness is on the byte(s) we load from that address. This is a mostly-harmless bug (since pointers on x64 are 64 bits wide, so signedness / unsignedness is a no-op), except it triggered a sanity-checking `assert` in x64hirtoasm.
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
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.
When we're doing, say, a
sgtcomparison on a memory address, we shouldn't make the pointer be signed: the signedness is on the byte(s) we load from that address. This is a mostly-harmless bug (since pointers on x64 are 64 bits wide, so signedness / unsignedness is a no-op), except it triggered a sanity-checkingassertin x64hirtoasm.