-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Swift 3.0] Fix s390x Enum load/storeMultiPayloadValue #4463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
tkremenek
merged 1 commit into
swiftlang:swift-3.0-branch
from
linux-on-ibm-z:swift-3.0-branch-s390x-enum
Aug 24, 2016
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
#endif
is now after the code that would previously had been available when__BIG_ENDIAN__
is not defined. Is this change intended?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also clearly a behavioral change here, but no test case reflecting that. I don't accepting this change would be acceptable for the
swift-3.0-branch
in the current state without a test case. It's also not clear to me if the change is correct, per my comment about the preprocessor guard.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review.
The code from lines 365-368 are still available when
__BIG_ENDIAN__
is not defined (as they are between#else
and#endif
). Nothing has changed for little endian platforms.The Interpreter/enum.swift test was failing on s390x and is now passing with this change. We didn't observe any regression in other tests with this change.
@garyliu1, FYI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Further explaining the move of the
#endif
...The new code between line 354-360 is the corresponding memset work required for big endian platforms. Therefore, the original memset code (which was common before) would need to be made specific for little endian platforms or else the big endian platform would perform another memset and corrupt the existing data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You both are absolutely right. Sorry for misreading the code. This looks perfectly safe to take.