-
Notifications
You must be signed in to change notification settings - Fork 5.9k
8300109: RISC-V: Improve code generation for MinI/MaxI nodes #11988
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
👋 Welcome back fyang! A progress list of the required criteria for merging this PR into |
@RealFYang 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
|
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'm curious to see some JMH results on 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 okay. I was wondering if it was possible to have multiple match(...)
-es per instruct
, so we could coalesce the symmetric "compare with zero" cases. But it is fine as it is.
@RealFYang 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 1 new commit 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 |
Good suggestion. Fixed in the last commit. Also corrected the pipeline for those nodes as discussed on #11919. |
Well, not that much (%3 at most) when I run the max & min tests in JMH test [1] on my unmatched board:
I think it will depend on the micro-architecture implementation. But the code generated should be always simplified in this case. |
Thanks all for the review. I will proceed integrating this if there is no other comments. |
/integrate |
Going to push as commit f1194dc.
Your commit was automatically rebased without conflicts. |
@RealFYang Pushed as commit f1194dc. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
As described by the issue, code generation for MinI/MaxI nodes on RISC-V could be improved when one of the source register is the same as the destination register. Also the code could be further simplified when that source register is constant 0 making use of the dedicated zero register of the architecture. This adds new match rules for those cases.
Testing:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11988/head:pull/11988
$ git checkout pull/11988
Update a local copy of the PR:
$ git checkout pull/11988
$ git pull https://git.openjdk.org/jdk pull/11988/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11988
View PR using the GUI difftool:
$ git pr show -t 11988
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11988.diff