Open
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
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.
You may have seen expressions like the following (using boogie syntax):
This is taken from main in cntlm. If we look closely, this is just a concatenation of the same singular bit over and over again! We could just replace it with a repeat.
But if you think about it, a repeat of a one bit value is the same thing as a sign extend.
But if you think about it even more, we're doing a logical right shift by 31 then taking the first bit, and then sign extending... That's just an arithmetic right shift!
I suspect that these big concat chain comes from somewhere in the lifting pipeline not knowing how to handle 32 bit arithmetic shifts nicely. Hopefully the simplification helps somewhere!