-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8334396: RISC-V: verify perf of ReverseBytesI/L #19750
Conversation
👋 Welcome back mli! A progress list of the required criteria for merging this PR into |
@Hamlin-Li 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 117 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 |
@Hamlin-Li 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. |
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 catch! Did you check the friends ReverseBytesS/ReverseBytesUS? It's very likely that they bear a similar peformance issue.
I think so too, but not yet check ReverseBytesS/ReverseBytesUS, I don't find the existing micro test for them, so I plan to put them in other pr's. And I created an umbrella bug at: https://bugs.openjdk.org/browse/JDK-8334395, am planning to go through (verify and fix) the intrinsics which might lead to potential performance regression gradually. |
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.
All right then! Thanks.
Hi, a Q. The cost in AD file is: Without ZBB it looks like it should be 17x. |
Seems the compiler will not decide whether to pick an intrinsic or just JIT it based on the cost of the supplied instrinsic. And I think the test result confirm this point. |
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.
Ok, thanks.
Thanks @robehn @RealFYang for your reviewing. |
/integrate |
Going to push as commit 6420846.
Your commit was automatically rebased without conflicts. |
@Hamlin-Li Pushed as commit 6420846. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
Can you help to review the patch?
The test data below shows that, if zbb is not supported on current hardware, then intrinsic brings perf regression rather than benefit.
So, ReverseBytesI/L should only be enabled when zbb is supported.
Test data
existing benchmark:
test/micro/org/openjdk/bench/java/lang/Longs.java, reverseBytes()
test/micro/org/openjdk/bench/java/lang/Integers.java, reverseBytes()
all tests running below with rvv disabled.
tested on K230-CanMV
-XX:-UseZbb, intrinsic enabled by default
o.o.b.j.lang.Integers.reverseBytes N/A 500 avgt 6128.125 ns/op
o.o.b.j.lang.Longs.reverseBytes N/A 500 avgt 10807.930 ns/op
-XX:+UseZbb, intrinsic enabled by default
o.o.b.j.lang.Integers.reverseBytes N/A 500 avgt 1788.990 ns/op
o.o.b.j.lang.Longs.reverseBytes N/A 500 avgt 1113.734 ns/op
-XX:-UseZbb, and disable ReverseBytesI/L instrinsic
o.o.b.j.lang.Integers.reverseBytes N/A 500 avgt 3552.902 ns/op
o.o.b.j.lang.Longs.reverseBytes N/A 500 avgt 4586.980 ns/op
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19750/head:pull/19750
$ git checkout pull/19750
Update a local copy of the PR:
$ git checkout pull/19750
$ git pull https://git.openjdk.org/jdk.git pull/19750/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 19750
View PR using the GUI difftool:
$ git pr show -t 19750
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19750.diff
Webrev
Link to Webrev Comment