-
Notifications
You must be signed in to change notification settings - Fork 6k
8322077: Add Ideal transformation: (~a) | (~b) => ~(a & b) #16334
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 CptGit! A progress list of the required criteria for merging this PR into |
@CptGit This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Hi, can I get a review? |
A JBS issue has been created for this: JDK-8322077. Please update the PR accordingly. |
Webrevs
|
Thanks. Updated. |
LGTM, but may you consider having dedicated functions to check and create |
Thanks. I updated. Please let me know if there are more comments. |
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. Please update the copyright dates.
I submitted testing and will report back once it passed.
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 like a good idea. Left a few comments.
I would have merged this with #16333, since it is essentially the symmetric case. But leave it separate now.
It would be nice to have some shared tests, where both optimizations need to be combined. Like:
(~a | ~b) & (~c | ~d)
-> ~(a & b) & ~(c & d)
-> ~((a & b) | (c & d))
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout ornode-PNewDeMorganLawOrToAnd
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
@CptGit 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 41 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@TobiHartmann, @eme64) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
@CptGit can you merge from master again, please? It looks now like you are pushing both the changes here and the ones from your previous PR. Once you did that, I'd like to run some testing before we push this. |
…NewDeMorganLawOrToAnd
@eme64 Yes I merged. Looks clean now. |
Testing running for commit 34... |
All tests passed, this is good to go. |
/integrate |
@eme64 @TobiHartmann Thanks for testing! Can you sponsor it when you get a chance thank you! |
/sponsor |
Going to push as commit 1515bd7.
Your commit was automatically rebased without conflicts. |
@TobiHartmann @CptGit Pushed as commit 1515bd7. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hello,
(~a) | (~b) => ~(a & b) is a widely seen pattern, for example it is implemented for LLVM here; however it is missing in current implementation of hotspot. This pull request adds this transformation and associated tests.
Thanks.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16334/head:pull/16334
$ git checkout pull/16334
Update a local copy of the PR:
$ git checkout pull/16334
$ git pull https://git.openjdk.org/jdk.git pull/16334/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16334
View PR using the GUI difftool:
$ git pr show -t 16334
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16334.diff
Webrev
Link to Webrev Comment