-
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
8312547: Max/Min nodes Value implementation could be improved #15021
Conversation
👋 Welcome back qamai! A progress list of the required criteria for merging this PR into |
@merykitty 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
|
// Either input is BOTTOM ==> the result is the local BOTTOM | ||
const Type *bot = bottom_type(); | ||
if( (t1 == bot) || (t2 == bot) || | ||
(t1 == Type::BOTTOM) || (t2 == Type::BOTTOM) ) |
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 don't think Type::BOTTOM
can appear here, there are other nodes (such as convert nodes) that do not check for Type::BOTTOM
. Maybe someone could shed light on this, please?
could you please check your change with jmh test ( numbers before and after the patch) : org/openjdk/bench/vm/compiler/MaxMinOptimizeTest.java just want to make sure it doesn't regress |
@VladimirKempik Thanks for taking a look, the results look the same both before and after the patch, which is expected given none of them would benefit from more precise values of max/min nodes, these are the numbers:
|
Thank 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.
Looks good to me.
@merykitty 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 56 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 |
@TobiHartmann Thanks for your reviews, I have adjusted the code style there. |
Hi, may I have a second review, please? |
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 am fine with fix and cleaning you did.
@vnkozlov Thanks a lot for your reviews, I will integrate the change. |
/integrate |
Going to push as commit 837cf85.
Your commit was automatically rebased without conflicts. |
@merykitty Pushed as commit 837cf85. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
This patch removes the early return in
AddNode::Value
in case one of the inputs is a bottom, which may affect the value calculation of nodes such asMin/MaxNode
.Please kindly review, thanks very much.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15021/head:pull/15021
$ git checkout pull/15021
Update a local copy of the PR:
$ git checkout pull/15021
$ git pull https://git.openjdk.org/jdk.git pull/15021/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15021
View PR using the GUI difftool:
$ git pr show -t 15021
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15021.diff
Webrev
Link to Webrev Comment