Skip to content
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

8251271: C2: Compile::_for_igvn list is corrupted after RenumberLiveNodes #713

Closed
wants to merge 2 commits into from

Conversation

@nhat-nguyen
Copy link
Contributor

@nhat-nguyen nhat-nguyen commented Oct 16, 2020

I'm following up on this thread http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2020-September/039910.html
I'm clearing for_igvn before restoring as suggested by Xin


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed

Testing

Linux x64 Windows x64 macOS x64
Build ✔️ (5/5 passed) ✔️ (2/2 passed) ✔️ (2/2 passed)
Test (tier1) ✔️ (9/9 passed) ✔️ (9/9 passed) ✔️ (9/9 passed)

Issue

  • JDK-8251271: C2: Compile::_for_igvn list is corrupted after RenumberLiveNodes

Reviewers

Download

$ git fetch https://git.openjdk.java.net/jdk pull/713/head:pull/713
$ git checkout pull/713

@bridgekeeper
Copy link

@bridgekeeper bridgekeeper bot commented Oct 16, 2020

👋 Welcome back nhat-nguyen! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

Loading

@openjdk openjdk bot added the rfr label Oct 16, 2020
@openjdk
Copy link

@openjdk openjdk bot commented Oct 16, 2020

@nhat-nguyen The following label will be automatically applied to this pull request:

  • hotspot-compiler

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.

Loading

@mlbridge
Copy link

@mlbridge mlbridge bot commented Oct 16, 2020

Webrevs

Loading

@navyxliu
Copy link
Contributor

@navyxliu navyxliu commented Oct 17, 2020

Looks good to me, but we need at least a reviewer to approve it.

Loading

// Restore the original for_igvn pointer for subsequent uses.
// Clear the for_igvn list because it may have irrelevant nodes
// from the previous PhaseRenumberLive run.
save_for_igvn->clear();

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since PhaseRenumberLive::PhaseRenumberLive moves nodes from for_igvn() to new_worklist, does it make more sense to drain original for_igvn() worklist there?

Loading

Copy link
Contributor

@navyxliu navyxliu Oct 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Loading

Copy link
Contributor Author

@nhat-nguyen nhat-nguyen Oct 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the suggestion. I have updated the PR.

Loading

Copy link
Contributor

@navyxliu navyxliu Oct 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Loading

Copy link

@iwanowww iwanowww left a comment

Looks good.

Loading

@openjdk
Copy link

@openjdk openjdk bot commented Oct 19, 2020

@nhat-nguyen 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:

8251271: C2: Compile::_for_igvn list is corrupted after RenumberLiveNodes

Reviewed-by: vlivanov

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 150 new commits pushed to the master branch:

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 (@iwanowww) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

Loading

@openjdk openjdk bot added the ready label Oct 19, 2020
@nhat-nguyen
Copy link
Contributor Author

@nhat-nguyen nhat-nguyen commented Oct 19, 2020

/integrate

Loading

@openjdk openjdk bot added the sponsor label Oct 19, 2020
@openjdk
Copy link

@openjdk openjdk bot commented Oct 19, 2020

@nhat-nguyen
Your change (at version 35835f8) is now ready to be sponsored by a Committer.

Loading

@TobiHartmann
Copy link
Member

@TobiHartmann TobiHartmann commented Oct 20, 2020

/sponsor

Loading

@openjdk
Copy link

@openjdk openjdk bot commented Oct 20, 2020

@TobiHartmann @nhat-nguyen Since your change was applied there have been 159 commits pushed to the master branch:

  • 98ec4a6: 8254805: compiler/debug/TestStressCM.java is still failing
  • 355f44d: 8254994: [x86] C1 StubAssembler::call_RT, "call_offset might not be initialized"
  • 0a75b37: 8254776: Remove unimplemented LowMemoryDetector::check_memory_usage
  • b65dcfa: 8197981: Missing return statement in __sync_val_compare_and_swap_8
  • 5b51085: 8254997: Remove unimplemented OSContainer::read_memory_limit_in_bytes
  • c87cdf7: 8254029: ObjectMonitor cleanup/minor bug-fix changes extracted from JDK-8253064
  • 7a580ca: 8255027: Problem list for Graal test gc/stress/TestStressG1Humongous.java
  • 6e8835c: 7110890: reg test TranslucentShapedFrameTest fails to create non-opaque frame
  • bf19581: 8255016: ConstantDescs.FALSE claims it represents TRUE
  • 0f4fb36: 8255032: Conflict between recent pushes breaks the build
  • ... and 149 more: https://git.openjdk.java.net/jdk/compare/c2a5de636fe44637f84fae76a8bb42524a7b2885...master

Your commit was automatically rebased without conflicts.

Pushed as commit 5fedfa7.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants