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

8250962: [lworld] C2 should not replace redundant scalar replaceable allocations #133

Closed
wants to merge 1 commit into from

Conversation

TobiHartmann
Copy link
Member

@TobiHartmann TobiHartmann commented Aug 4, 2020

When searching for multiple allocations of an inline type, ignore scalar replaceable ones because they will be removed anyway and changing the memory chain will confuse other optimizations.


Progress

  • Change must not contain extraneous whitespace

Issue

  • JDK-8250962: [lworld] C2 should not replace redundant scalar replaceable allocations

Download

$ git fetch https://git.openjdk.java.net/valhalla pull/133/head:pull/133
$ git checkout pull/133

@bridgekeeper
Copy link

@bridgekeeper bridgekeeper bot commented Aug 4, 2020

👋 Welcome back thartmann! A progress list of the required criteria for merging this PR into lworld will be added to the body of your pull request.

@openjdk
Copy link

@openjdk openjdk bot commented Aug 4, 2020

@TobiHartmann This change now passes all automated pre-integration checks, type /integrate in a new comment to proceed. After integration, the commit message will be:

8250962: [lworld] C2 should not replace redundant scalar replaceable allocations
  • If you would like to add a summary, use the /summary command.
  • To credit additional contributors, use the /contributor command.
  • To add additional solved issues, use the /issue command.

Since the source branch of this PR was last updated there have been 2 commits pushed to the lworld branch:

  • e473d9d: 8244315: [lworld] The hierarchy between V$ref and V$val must be sealed
  • 5305fbd: 8244314: [lworld] V.ref and V.val are supposed to be nest mates

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge lworld into your branch, and then specify the current head hash when integrating, like this: /integrate e473d9d4d8e385f248b95d66efbb50f36c4a4745.

➡️ To integrate this PR with the above commit message to the lworld branch, type /integrate in a new comment.

@mlbridge
Copy link

@mlbridge mlbridge bot commented Aug 4, 2020

Webrevs

@TobiHartmann
Copy link
Member Author

@TobiHartmann TobiHartmann commented Aug 4, 2020

/integrate

@openjdk openjdk bot closed this Aug 4, 2020
@openjdk openjdk bot added integrated and removed ready rfr labels Aug 4, 2020
@openjdk
Copy link

@openjdk openjdk bot commented Aug 4, 2020

@TobiHartmann The following commits have been pushed to lworld since your change was applied:

  • e473d9d: 8244315: [lworld] The hierarchy between V$ref and V$val must be sealed
  • 5305fbd: 8244314: [lworld] V.ref and V.val are supposed to be nest mates

Your commit was automatically rebased without conflicts.

Pushed as commit ef1a221.

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