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
8264173: [s390] Improve Hardware Feature Detection And Reporting #3196
Conversation
👋 Welcome back lucy! A progress list of the required criteria for merging this PR into |
Webrevs
|
/cc hotspot-compiler |
@RealLucy |
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.
I didn't expect the change to become that large. But it looks good to me. The lengthy output only gets generated with -XX:+Verbose. That's fine.
"system-z, g7-z13, ldisp_fast, extimm, pcrel_load/store, cmpb, cond_load/store, interlocked_update, txm, vectorinstr", | ||
"system-z, g8-z14, ldisp_fast, extimm, pcrel_load/store, cmpb, cond_load/store, interlocked_update, txm, vectorinstr, instrext2, venh1)", | ||
"system-z, g9-z15, ldisp_fast, extimm, pcrel_load/store, cmpb, cond_load/store, interlocked_update, txm, vectorinstr, instrext2, venh1, instrext3, VEnh2 )" | ||
}; |
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.
Would be nice to generate the feature string from a table it instead of having so many copies. But I'm ok with it for now.
if (Verbose) { | ||
print_features(); | ||
if (Verbose || PrintAssembly || PrintStubCode) { | ||
print_features_internal("CPU Version as detected internally: ", PrintAssembly || PrintStubCode); |
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.
2 spaces while other usages have no spaces?
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.
You are right. These spaces were excessive. Now they are gone.
@RealLucy 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 161 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 |
Thank you for the review, Martin! |
LGTM |
Thank you Goetz! |
/integrate |
@RealLucy Since your change was applied there have been 161 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit d3fdd73. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This enhancement is intended to improve the hardware feature detection and reporting, in particular for more recently introduced hardware. The enhancement is a prerequisite for possible future feature exploitation.
Reviews are highly welcome and appreciated.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3196/head:pull/3196
$ git checkout pull/3196
Update a local copy of the PR:
$ git checkout pull/3196
$ git pull https://git.openjdk.java.net/jdk pull/3196/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3196
View PR using the GUI difftool:
$ git pr show -t 3196
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3196.diff