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
8253690: [PPC64] Use flag kind "diagnostic" for platform specific flags #413
Conversation
👋 Welcome back mdoerr! A progress list of the required criteria for merging this PR into |
@TheRealMDoerr 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.
Hi Martin,
make sure you check up on the places the switches are used and pass UnlockDiagnosticVMOptions.
Cheers, Thomas
"Reoptimize code-sequences of calls at runtime.") \ | ||
\ | ||
/* Power 8: Configure Data Stream Control Register. */ \ | ||
product(uint64_t,DSCR_PPC64, (uintx)-1, \ | ||
product(uint64_t, DSCR_PPC64, (uint64_t)-1, \ |
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.
Has nothing to do with this issue. But I leave it up to you.
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.
Just cleanup, no real change.
/* special instructions */ \ | ||
product(bool, UseByteReverseInstructions, false, \ | ||
product(bool, SuperwordUseVSX, false, \ |
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.
Why leave this one out?
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.
SuperwordUseVSX switches usage of vector registers in C2. It's more fundamental than simple instruction usage switches. It's comparable to UseAVX on x86 which is product, too. So I prefer keeping it product for now. Are you ok with it?
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.
Sure, just curious. Leave it up to you.
\ | ||
product(bool, ZapMemory, false, "Write 0x0101... to empty memory." \ | ||
" Use this to ease debugging.") \ |
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.
Future cleanup: this feels like it should be in shared code. The usual way to do this is to zap in DEBUG.
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.
Yeah, sounds like this functionality derserves some overwork. But I only want to make it diagnostic with this change.
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 Martin.
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.
This is an overdue cleanup. Thanks for taking care. The changes look good to me. Reviewed.
/integrate |
@TheRealMDoerr This PR has not yet been marked as ready for integration. |
@TheRealMDoerr 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 more 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 54 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 |
/integrate |
@TheRealMDoerr Since your change was applied there have been 54 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit a824289. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Current platform implementation (globals_ppc.hpp) uses regular product flags for almost everything.
Most platform specific flags were never intended for official support. They are only there to diagnose issues and find workarounds.
So flag kind "diagnostic" fits better for them.
Note that I rearranged a couple of lines when looking at the diff.
My actual change is what is described here: https://bugs.openjdk.java.net/browse/JDK-8253692
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/413/head:pull/413
$ git checkout pull/413