Fix for incorrect MoveDataType #692
Merged
Conversation
This file contains 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
TR::Address and TR_GPR should correspond to TR_MovDataTypes::Int4 on X86-32, while previous code always returns TR_MovDataTypes::Int8 Signed-off-by: Victor Ding <dvictor@ca.ibm.com>
|
These look like legitimate oopses - LGTM |
vijaysun-omr
approved these changes
Jan 24, 2017
|
Fix datatypes based on bit-ness. Merging. |
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.
TR::Address and TR_GPR should correspond to TR_MovDataTypes::Int4 on X86-32,
while previous code always returns TR_MovDataTypes::Int8
Signed-off-by: Victor Ding dvictor@ca.ibm.com