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

8348599: [lworld] Unsafe.getValue() and Unsafe.putValue() have expensive lookup code #1336

Closed
wants to merge 1 commit into from

Conversation

fparain
Copy link
Collaborator

@fparain fparain commented Jan 24, 2025

New version of Unsafe methods to read and write flat values.
More details in the CR.


Progress

  • Change must not contain extraneous whitespace

Issue

  • JDK-8348599: [lworld] Unsafe.getValue() and Unsafe.putValue() have expensive lookup code (Bug - P3)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/valhalla.git pull/1336/head:pull/1336
$ git checkout pull/1336

Update a local copy of the PR:
$ git checkout pull/1336
$ git pull https://git.openjdk.org/valhalla.git pull/1336/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1336

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/valhalla/pull/1336.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jan 24, 2025

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

@openjdk
Copy link

openjdk bot commented Jan 24, 2025

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

8348599: [lworld] Unsafe.getValue() and Unsafe.putValue() have expensive lookup code

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

  • 287a7b5: 8348428: [lworld] ProcessReaper stack size too small in debug build

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

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

@mlbridge
Copy link

mlbridge bot commented Jan 24, 2025

Webrevs

@fparain
Copy link
Collaborator Author

fparain commented Jan 27, 2025

/integrate

@openjdk
Copy link

openjdk bot commented Jan 27, 2025

Going to push as commit 4d7ba02.
Since your change was applied there has been 1 commit pushed to the lworld branch:

  • 287a7b5: 8348428: [lworld] ProcessReaper stack size too small in debug build

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated label Jan 27, 2025
@openjdk openjdk bot closed this Jan 27, 2025
@openjdk
Copy link

openjdk bot commented Jan 27, 2025

@fparain Pushed as commit 4d7ba02.

💡 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
Development

Successfully merging this pull request may close these issues.

1 participant