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

8262726: AArch64: C1 StubAssembler::call_RT can corrupt stack #145

Closed
wants to merge 1 commit into from
Closed

8262726: AArch64: C1 StubAssembler::call_RT can corrupt stack #145

wants to merge 1 commit into from

Conversation

@snazarkin
Copy link

@snazarkin snazarkin commented Mar 12, 2021


Progress

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

Issue

  • JDK-8262726: AArch64: C1 StubAssembler::call_RT can corrupt stack

Download

$ git fetch https://git.openjdk.java.net/jdk13u-dev pull/145/head:pull/145
$ git checkout pull/145

Sergey
@bridgekeeper
Copy link

@bridgekeeper bridgekeeper bot commented Mar 12, 2021

👋 Welcome back snazarki! 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 be67aaabe63a4440c64bf79b9fa0d1394ac87ddf 8262726: AArch64: C1 StubAssembler::call_RT can corrupt stack Mar 12, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Mar 12, 2021

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

@openjdk
Copy link

@openjdk openjdk bot commented Mar 12, 2021

@snazarkin This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8262726: AArch64: C1 StubAssembler::call_RT can corrupt stack

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 master branch:

  • 55f25d1: 7185258: [macosx] Deadlock in SunToolKit.realSync()

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

➡️ 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).

@snazarkin
Copy link
Author

@snazarkin snazarkin commented Mar 12, 2021

/integrate

@mlbridge
Copy link

@mlbridge mlbridge bot commented Mar 12, 2021

Webrevs

@openjdk openjdk bot added the sponsor label Mar 12, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Mar 12, 2021

@snazarkin
Your change (at version 9957e69) is now ready to be sponsored by a Committer.

@yan-too
Copy link
Collaborator

@yan-too yan-too commented Mar 12, 2021

/sponsor

@openjdk openjdk bot closed this Mar 12, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Mar 12, 2021

@yan-too @snazarkin Since your change was applied there has been 1 commit pushed to the master branch:

  • 55f25d1: 7185258: [macosx] Deadlock in SunToolKit.realSync()

Your commit was automatically rebased without conflicts.

Pushed as commit 5de1b46.

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

@openjdk openjdk bot removed the rfr label Mar 12, 2021
@snazarkin snazarkin deleted the snazarkin:8262726-backport branch Mar 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants