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

8201516: DebugNonSafepoints generates incorrect information #1268

Closed
wants to merge 2 commits into from

Conversation

apangin
Copy link

@apangin apangin commented Apr 19, 2023

Hi,

This is a backport of JDK-8201516: DebugNonSafepoints generates incorrect information

Original patch applies cleanly, except that for the jtreg test where I removed unsupported phase = CompilePhase.BEFORE_MATCHING. I verified that the test passes with the patch but fails without.

Testing: x86_64 build, tier1

Thanks!


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8201516: DebugNonSafepoints generates incorrect information

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1268/head:pull/1268
$ git checkout pull/1268

Update a local copy of the PR:
$ git checkout pull/1268
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1268/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1268

View PR using the GUI difftool:
$ git pr show -t 1268

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1268.diff

Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 19, 2023

👋 Welcome back apangin! 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.

@openjdk openjdk bot changed the title Backport 94eda53d98e5011cc613d031ff8941e254eb666b 8201516: DebugNonSafepoints generates incorrect information Apr 19, 2023
@openjdk
Copy link

openjdk bot commented Apr 19, 2023

This backport pull request has now been updated with issue from the original commit.

@openjdk openjdk bot added backport rfr Pull request is ready for review labels Apr 19, 2023
@apangin
Copy link
Author

apangin commented Apr 19, 2023

/label hotspot-compiler

@mlbridge
Copy link

mlbridge bot commented Apr 19, 2023

Webrevs

@openjdk
Copy link

openjdk bot commented Apr 19, 2023

@apangin
The label hotspot-compiler is not a valid label.
These labels are valid:

@openjdk
Copy link

openjdk bot commented Apr 19, 2023

@apangin Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

Copy link
Member

@TobiHartmann TobiHartmann left a 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.

@openjdk
Copy link

openjdk bot commented Apr 19, 2023

@apangin 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:

8201516: DebugNonSafepoints generates incorrect information

Reviewed-by: thartmann, shade

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 40 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 (@TobiHartmann, @shipilev) 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).

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Apr 19, 2023
@apangin
Copy link
Author

apangin commented Apr 20, 2023

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Apr 20, 2023
@openjdk
Copy link

openjdk bot commented Apr 20, 2023

@apangin
Your change (at version b57ec39) is now ready to be sponsored by a Committer.

@shipilev
Copy link
Member

The push approval is there.

/sponsor

@openjdk
Copy link

openjdk bot commented Apr 20, 2023

Going to push as commit 9d6f1d7.
Since your change was applied there have been 40 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Apr 20, 2023
@openjdk openjdk bot closed this Apr 20, 2023
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Apr 20, 2023
@openjdk
Copy link

openjdk bot commented Apr 20, 2023

@shipilev @apangin Pushed as commit 9d6f1d7.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants