-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8329254: optimize integral reverse operations on x86 GFNI target. #18530
Conversation
👋 Welcome back jbhateja! A progress list of the required criteria for merging this PR into |
@jatin-bhateja 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 173 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 |
/label add hotspot-compiler-dev |
@jatin-bhateja |
Webrevs
|
@jatin-bhateja Thanks a lot for putting this PR together. The register class for the following two instructs in x86_64.ad also need change: To: |
Hi @sviswa7 , GFNI is supported on Icelake+ CPUs, with regD/F register classes we select entire range of registers xmm1-31 on AVX512 targets which gives freedom to assembler to auto-promote instruction to EVEX encoding if allocator assigned a register from higher register bank, in this case since instruction operands are 128 bit registers, in principle an autopromotion on AVX512 target will only be feasible if target support VL, but given that all AVX512 GFNI targets support vector length orthogonality hence we should be good to go. I still agree that it's good to be strict than keeping loose ends, given that cloud instances can be tuned to enable custom feature sets. |
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.
/integrate |
Going to push as commit b04b304.
Your commit was automatically rebased without conflicts. |
@jatin-bhateja Pushed as commit b04b304. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Efficient GFNI based instruction sequence to compute integral reverse operation was added along with JEP-426 (VectorAPI 4th Incubation). https://bugs.openjdk.org/browse/JDK-8284960
However, the CPUID based feature detection for GFNI was incorrectly performed under AVX512 check, fixing it shows roughly 2X performance improvement for Integer/Long.reverse APIs on E-core targets (MTL+).
Kindly review.
Best Regards,
Jatin
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18530/head:pull/18530
$ git checkout pull/18530
Update a local copy of the PR:
$ git checkout pull/18530
$ git pull https://git.openjdk.org/jdk.git pull/18530/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18530
View PR using the GUI difftool:
$ git pr show -t 18530
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18530.diff
Webrev
Link to Webrev Comment