-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8293999: [JVMCI] need support for aligned constants in generated code larger than 8 bytes #10392
8293999: [JVMCI] need support for aligned constants in generated code larger than 8 bytes #10392
Conversation
👋 Welcome back bulasevich! A progress list of the required criteria for merging this PR into |
@bulasevich 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. |
9823817
to
86a1e9a
Compare
86a1e9a
to
851d58b
Compare
7a08f87
to
80693ef
Compare
Webrevs
|
src/hotspot/share/asm/codeBuffer.hpp
Outdated
#if INCLUDE_JVMCI | ||
if (EnableJVMCI) { | ||
// Graal vectorization requires larger aligned constants | ||
return 64; |
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 means all Graal installed code will pay a penalty even though most installed code does not include constants that need such large alignment. It would be preferable to allow a compiler to specify the alignment requirement per nmethod.
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 agree. The alignment should probably be a field in CodeBuffer with a default value of 8.
@bulasevich Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information. |
… larger than 8 bytes
… alignment for all JVMCI nmethods
f743a42
to
59ff8c4
Compare
@bulasevich Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information. |
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.
@bulasevich 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 6 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
src/hotspot/share/asm/codeBuffer.hpp
Outdated
@@ -456,6 +454,9 @@ class CodeBuffer: public StackObj DEBUG_ONLY(COMMA private Scrubber) { | |||
_insts.initialize_outer(this, SECT_INSTS); | |||
_stubs.initialize_outer(this, SECT_STUBS); | |||
|
|||
// default value. should be changed if vectorization requires large aligned constants |
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 would not make this comment so vectorization specific. Just say something like:
// Default is to align on 8 bytes. A compiler can change this
// if larger alignment (e.g., 32-byte vector masks) is required.
thanks! |
/integrate |
Going to push as commit f3ca0ca.
Your commit was automatically rebased without conflicts. |
@bulasevich Pushed as commit f3ca0ca. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10392/head:pull/10392
$ git checkout pull/10392
Update a local copy of the PR:
$ git checkout pull/10392
$ git pull https://git.openjdk.org/jdk pull/10392/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10392
View PR using the GUI difftool:
$ git pr show -t 10392
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10392.diff