-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8264018: AArch64: NEON loadV2 and storeV2 addressing is wrong #3168
Conversation
AArch64 c2 loadV2 and storeV2 are used for Vector API mask value load/store with size of halfword. Their load/store immediate offset should be similar to other vector load/store, e.g. loadV4/storeV4, valid only for unscaled signed offset of imm9 or scaled unsigned offset of imm12:scale. Verified with tier1 and vector api cases, though I cannot reproduce this issue.
👋 Welcome back njian! A progress list of the required criteria for merging this PR into |
I admire your decision to tidy up the files, but I can't easily see what exactly has changed. |
The change is to the memory operand of the first load and store rules. It was special cased to memory and is now vmem2 (just as the relocated rules used vmem4, vmem8 etc). |
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.
@nsjian 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 11 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 |
I should explain the change in my PR comment better. I have two commits in this PR, the first commit is the main change to fix the issue, which adds vmem2 opclass for loadv2 and storev2, as their imm address ranges should be different from others. The second commit is the code tidy up. |
Ah, so it is. My mistake. |
Thank you for the review! @adinn @theRealAph |
/integrate |
@nsjian Since your change was applied there have been 29 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 3e18330. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
AArch64 c2 loadV2 and storeV2 are used for Vector API mask value load/store with size of halfword. Their load/store immediate offset should be similar to other vector load/store, e.g. loadV4/storeV4, valid only for unscaled signed offset of imm9 or scaled unsigned offset of imm12:scale. This patch also groups other loadVs/storeVs together in the ad file.
Verified with tier1 and jtreg vector api cases, though I cannot reproduce this issue.
Progress
Issue
Reviewers
Download
To checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3168/head:pull/3168
$ git checkout pull/3168
To update a local copy of the PR:
$ git checkout pull/3168
$ git pull https://git.openjdk.java.net/jdk pull/3168/head