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
8281544: assert(VM_Version::supports_avx512bw()) failed for Tests jdk/incubator/vector/ #7510
Conversation
…/incubator/vector/
|
Webrevs
|
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.
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!
@eme64 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 60 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 (@vnkozlov, @neliasso, @TobiHartmann) but any other Committer may sponsor as well.
|
/label add hotspot-compiler |
@neliasso |
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.
Thanks @neliasso @TobiHartmann @vnkozlov for the reviews! |
/sponsor |
Going to push as commit 4e0b81c.
Your commit was automatically rebased without conflicts. |
@TobiHartmann @eme64 Pushed as commit 4e0b81c. |
ZSaveLiveRegisters::ZSaveLiveRegisters
stores live registers, and later they are loaded again.This includes opmask registers, which are part of AVX512. However, not all platforms have all of the AVX512 instructions.
For example Knights Landing has general AVX512 support and makes use of optmask registers, but does not support the AVX512 BW subset of instructions, specifically it does not support the
kmovql
instruction. Platforms like Cannon Landing have support for AVX512 BW.Solution: in analogy to
RegisterSaver::save_live_registers
, which seems to perform a very similar task, useMacroAssembler::kmov
instead ofkmovql
directly. Internally,kmov
choses eitherkmovql
if avx512bw is available, else it takeskmovwl
.As a regression test, I took one of the tests that failed with
-XX:+UnlockExperimentalVMOptions -XX:+UseZGC
, and added an additional@run
statement with those flags. I simulated this test locally with Intel Software Development Emulator:sde -knl
: Knights Landing, AVX512 but not BW, fails without change tokmov
, passes with it.sde -cnl
: Cannon Landing, has AVX512 BW, passes before and after code change.Ran additional tests to verify that the test triggers before code change, and that with the code change nothing broke.
@neliasso Thanks for the help!
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7510/head:pull/7510
$ git checkout pull/7510
Update a local copy of the PR:
$ git checkout pull/7510
$ git pull https://git.openjdk.java.net/jdk pull/7510/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 7510
View PR using the GUI difftool:
$ git pr show -t 7510
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7510.diff