-
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
8288897: Clean up node dump code #9234
Conversation
👋 Welcome back epeter! A progress list of the required criteria for merging this PR into |
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.
Otherwise, nice cleanup! I think it's the right thing to remove unused and unmaintained dump
methods and reduce code duplication.
Have you checked that the printed node order with dump(X)
is the same as before? I'm not sure if that is a strong requirement. I'm just thinking about PrintIdeal
with which we do:
jdk/src/hotspot/share/opto/compile.cpp
Line 554 in 17aacde
root()->dump(9999); |
Some tools/scripts might depend on the previous order of dump(X)
. But I'm currently not aware of any such order-dependent processing. For the IR framework, the node order does not matter and if I see that correctly, the dump of an individual node is the same as before. So, it should be fine.
2 style fixes by Christian Co-authored-by: Christian Hagedorn <christian.hagedorn@oracle.com>
I did try to make sure that the output of |
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.
nice feature!
LGTM. I am not a reviewer. we still needs other reviewers to approve it.
I also verify that. root()->dump(9999) is still same.
|
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.
still LGTM. thanks.
@eme64 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! |
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 was out on vacation and only had the chance to have a look it again now. Thanks for doing the updates and verifying that the order is still the same! Thanks @navyxliu for double checking it as well! The colorful dump looks really nice :)
Thanks,
Christian
@eme64 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 331 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 |
Thanks @chhagedorn @navyxliu for the review and comments! |
Going to push as commit dbb2c4b.
Your commit was automatically rebased without conflicts. |
I recently did some work in the area of
Node::dump
andNode::find
, see JDK-8287647 and JDK-8283775.This change sets cleans up the code around, and tries to reduce code duplication.
Things I did:
dump(int)
to usedump_bfs
(reduce code duplication).dump_bfs
, focusing on output types. Mixed type is now also control if it has control output, and memory if it has memory output, etc. Plus, a node is also in the control category if itis_CFG
. This makesdump_bfs
much more usable, to traverse control and memory flow.call from debugger
comment to VM functions that are useful in debuggerfind_node_by_name
tofind_nodes_by_name
andfind_node_by_dump
tofind_nodes_by_dump
.PrintIdealIndentThreshold
(notproduct)Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9234/head:pull/9234
$ git checkout pull/9234
Update a local copy of the PR:
$ git checkout pull/9234
$ git pull https://git.openjdk.org/jdk pull/9234/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9234
View PR using the GUI difftool:
$ git pr show -t 9234
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9234.diff