-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8313438: [s390x] build broken after JDK-8301996 #15885
Conversation
👋 Welcome back amitkumar! A progress list of the required criteria for merging this PR into |
@offamitkumar The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
b8b5c5a
to
5c381ef
Compare
e383004
to
d17a366
Compare
d17a366
to
4d2e1de
Compare
Hi @RealLucy , @TheRealMDoerr Please consider to review this PR, as per your availability. Thank you. |
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.
Looks basically good, but I have a couple of questions and suggestions.
|
||
// Displacement is 0. No need to care about limited displacement range. | ||
const Address field(fieldAddr); | ||
__ lgr_if_needed(fieldAddr, off); |
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.
Was there a problem with the range? Why did it work in the old implementation?
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 comment is related to the uses of field. Depending on the instruction, disc is limited to be uimm12 or simm20. But the Address object is with displacement == 0.
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.
I didn't get why the separate agr
instructions are needed as part of this PR. Isn't that a separate issue?
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.
Martin, Are you referring to the fix for preserving flag
register value till the end ?
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.
If you want that this case to be handled in separate PR, then I'll file a JBS issue.
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.
I need an explanation why this code was changed this way. If it is required for this PR, please explain in comments. If it's a separate issue, please handle separately.
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.
Oh, Issue was with the flag
register value. We need to check the volatility at the end of putfield_or_static
method. And previous implementation was not preserving the value till the end, why it was working then ? That I don't know.
Current Implementation uses z_tmp_1
for saving flag
value till end. obj
now points to Z_ARG5
which is also pointed by oopStore_tmp2
, and if we don't use agr
then in case of object/atos
, will run into Multiple usecase for Z_R6
error from do_oop_store()
method .
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.
Is the agr only used to save a register? That should be explained in the comments. I believe it's only needed for the object case, right?
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 prior implementation used two non-volatile registers. Due to register shortage, only one register can be used. Penalty: compute the sum of obj and off explicitly immediately after the obj pointer is popped from stack. In the non-static case, this can't be done upfront.
|
||
// Displacement is 0. No need to care about limited displacement range. | ||
const Address field(fieldAddr); | ||
__ lgr_if_needed(fieldAddr, off); |
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 comment is related to the uses of field. Depending on the instruction, disc is limited to be uimm12 or simm20. But the Address object is with displacement == 0.
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.
I couldn't spot any obvious bug. Changes lgtm.
@offamitkumar This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 26 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
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.
Looks good to me, finally.
Thank you for patiently considering all the comments and change requests.
|
||
// Displacement is 0. No need to care about limited displacement range. | ||
const Address field(fieldAddr); | ||
__ lgr_if_needed(fieldAddr, off); |
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 prior implementation used two non-volatile registers. Due to register shortage, only one register can be used. Penalty: compute the sum of obj and off explicitly immediately after the obj pointer is popped from stack. In the non-static case, this can't be done upfront.
Thank you Martin, Lutz. For your valuable reviews & suggestions. /integrate |
Going to push as commit 7976151.
Your commit was automatically rebased without conflicts. |
@offamitkumar Pushed as commit 7976151. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Build Fix after JDK-8301996.
Warnings related to new Lightweight locking scheme are seen during the build phase, but we will get rid of them, after integrating #14414 . Testing done for
release-vm
,slowdebug-vm
,fastdebug-vm
andoptimized-vm
.3 Test failures seen on s390x are un-related to these changes.
JBS issue for test failures: JDK-8317581.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15885/head:pull/15885
$ git checkout pull/15885
Update a local copy of the PR:
$ git checkout pull/15885
$ git pull https://git.openjdk.org/jdk.git pull/15885/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15885
View PR using the GUI difftool:
$ git pr show -t 15885
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15885.diff
Webrev
Link to Webrev Comment