-
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
8290485: [vector] REVERSE_BYTES for byte type should not emit any instructions #9565
Conversation
👋 Welcome back xgong! A progress list of the required criteria for merging this PR into |
@XiaohongGong 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. |
Hi, could anyone please help to take a look at this simple patch? Thanks a lot for your time! |
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. I'll run some testing and report back once it passed.
@XiaohongGong 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 113 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 |
Thanks for the review and testing @TobiHartmann ! |
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.
Good.
Thanks for the review @vnkozlov ! |
/integrate |
Going to push as commit a6faf5d.
Your commit was automatically rebased without conflicts. |
@XiaohongGong Pushed as commit a6faf5d. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
I‘m sorry that I was in mistake for that the tests had passed, so I integrated this PR. If any tests fail I will revert this PR and fix it. Thanks! |
Testing passed and results are good. I looked. |
That's great! Thanks so much for that! |
The Vector API unary operation "
REVERSE_BYTES
" should not emit any instructions for byte vectors. The same to the relative masked operation. Currently it emits"mov dst, src"
on aarch64 when the "dst
" and "src
" are not the same register. But for the masked "REVERSE_BYTES
", the compiler will always generate a "VectorBlend
" which I think is redundant, since the first and second vector input is the same one. Please see the generated codes for the masked "REVERSE_BYTES
" for byte type with NEON:The elements in register "
v17
" and "v16
" are the same to each other, so the elements in result of "bsl
" is the same to the original loaded values in "v16
", no matter what the values in the vector mask are.To improve this, we can add the igvn transformations for "
ReverseBytesV
" and "VectorBlend
" in compiler. For "ReverseBytesV
", it can return the vector input if the basic element type isT_BYTE
. And for "VectorBlend
", it can return the first input if the first and the second input are the same one.Here is the performance data for the jmh benchmark [1] on ARM NEON:
This patch may not have any influence to the non-masked "
REVERSE_BYTES
" on ARM NEON, because the backend may not emit any instruction for it before.And here is the performance data on an x86 system:
[1] https://github.com/openjdk/panama-vector/blob/vectorIntrinsics/test/micro/org/openjdk/bench/jdk/incubator/vector/operation/ByteMaxVector.java#L2201
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9565/head:pull/9565
$ git checkout pull/9565
Update a local copy of the PR:
$ git checkout pull/9565
$ git pull https://git.openjdk.org/jdk pull/9565/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9565
View PR using the GUI difftool:
$ git pr show -t 9565
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9565.diff