-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8339063: [aarch64] Skip verify_sve_vector_length after native calls if SVE supports 128 bits VL only #20724
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
Conversation
…ports 128 bits VL only
👋 Welcome back jzhu! A progress list of the required criteria for merging this PR into |
@JoshuaZhuwj 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 66 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 (@adinn, @fg1417) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@JoshuaZhuwj 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. |
Webrevs
|
Add some more background. The maximum SVE vector length "VLmax" is determined by the hardware: 16 <= VLmax <= 256. Once we find cpu's VLMax is 16 bytes only, the verification "verify_sve_vector_length()" after native calls is not required - in other words, VL cannot be configured to a value other than 16. |
/label add hotspot-compiler |
@JoshuaZhuwj |
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.
The code changes look ok. What have you done to test it?
@adinn Thanks for your review!
I checked the behavior of prctl(PR_SVE_SET_VL, value) by a separated C case. I have an aarch64 hardware at hand with only 128-bit SVE vector length. I also ensure no regression failures by jtreg case: |
Ok, that sounds like it is sufficient. |
@@ -155,7 +155,7 @@ source %{ | |||
} | |||
|
|||
int length_in_bytes = vlen * type2aelembytes(bt); | |||
if (UseSVE == 0 && length_in_bytes > 16) { | |||
if (UseSVE == 0 && length_in_bytes > FloatRegister::neon_vl) { |
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.
Should we also update aarch64_vector_ad.m4
to avoid any mismatch :) ?
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.
Nice catch! I overlooked this place. Thanks for your reminder!
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.
LGTM! Thanks for the update.
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.
still good
/integrate |
@JoshuaZhuwj |
/sponsor |
Going to push as commit 0e6bb51.
Your commit was automatically rebased without conflicts. |
@adinn @JoshuaZhuwj Pushed as commit 0e6bb51. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this minor enhancement that skips verify_sve_vector_length after native calls.
It works on SVE micro-architecture that only supports 128-bit vector length.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/20724/head:pull/20724
$ git checkout pull/20724
Update a local copy of the PR:
$ git checkout pull/20724
$ git pull https://git.openjdk.org/jdk.git pull/20724/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 20724
View PR using the GUI difftool:
$ git pr show -t 20724
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/20724.diff
Webrev
Link to Webrev Comment