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
8255065: Zero: accessor_entry misses the IRIW case #766
Conversation
|
Good catch! I don't think anybody uses zero for PPC64, but it's better to get this fixed. Thanks.
@shipilev This change now passes all automated pre-integration checks. 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 15 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.
|
/integrate |
@shipilev Since your change was applied there have been 47 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit bd45191. |
While doing a change in related area, I noticed there is no IRIW handling block in
ZeroInterpreter::accessor_entry
when reading volatile fields. This probably breaks PPC64 Zero.There is a block in
bytecodeInterpreter.cpp
for common field access:Attention @TheRealMDoerr ;)
Testing:
Progress
Testing
Failed test tasks
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/766/head:pull/766
$ git checkout pull/766