-
Notifications
You must be signed in to change notification settings - Fork 235
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
8288865: [aarch64] LDR instructions must use legitimized addresses #1164
Conversation
👋 Welcome back apavlyutkin! A progress list of the required criteria for merging this PR into |
ping |
@apavlyutkin 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 85 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@theRealAph) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@apavlyutkin |
/sponsor |
Going to push as commit 1f40289.
Your commit was automatically rebased without conflicts. |
@yan-too @apavlyutkin Pushed as commit 1f40289. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi!
Please review the fix to non-volatile memory access on aarch64 that makes LDR instructions to use legitimized addresses exactly like it was done to STR instruction by https://bugs.openjdk.org/browse/JDK-8235385.
Verification (18.04.6 LTS / aarch64):
test/hotspot/jtreg/compiler/unsafe/NonVolatileMemoryAccessWithLongOffset.java
passes 10 of 10 runs. At least a half of runs failed before the fix.
Regression (18.04.6 LTS / aarch64): hotspot_compiler
@theRealAph @sandlerwang could you look at that? Thank you
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev pull/1164/head:pull/1164
$ git checkout pull/1164
Update a local copy of the PR:
$ git checkout pull/1164
$ git pull https://git.openjdk.org/jdk11u-dev pull/1164/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1164
View PR using the GUI difftool:
$ git pr show -t 1164
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/1164.diff