Skip to content

8305746: InitializeEncoding should cache Charset object instead of charset name #13499

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

Closed
wants to merge 3 commits into from

Conversation

peter-hofer
Copy link

@peter-hofer peter-hofer commented Apr 17, 2023

Store Charset object in jnuEncoding and use String(byte[], Charset) and String.getBytes(Charset) instead of passing the charset name.


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-8305746: InitializeEncoding should cache Charset object instead of charset name

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 13499

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13499.diff

Webrev

Link to Webrev Comment

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Apr 17, 2023
@bridgekeeper
Copy link

bridgekeeper bot commented Apr 17, 2023

Hi @peter-hofer, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user peter-hofer" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@peter-hofer
Copy link
Author

/covered

@bridgekeeper bridgekeeper bot added the oca-verify Needs verification of OCA signatory status label Apr 17, 2023
@bridgekeeper
Copy link

bridgekeeper bot commented Apr 17, 2023

Thank you! Please allow for a few business days to verify that your employer has signed the OCA. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@openjdk
Copy link

openjdk bot commented Apr 17, 2023

@peter-hofer The following label will be automatically applied to this pull request:

  • core-libs

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.

@openjdk openjdk bot added the core-libs core-libs-dev@openjdk.org label Apr 17, 2023
@peter-hofer
Copy link
Author

@naotoj please find here my changes to InitializeEncoding.

@bridgekeeper bridgekeeper bot removed oca Needs verification of OCA signatory status oca-verify Needs verification of OCA signatory status labels Apr 18, 2023
@openjdk openjdk bot added the rfr Pull request is ready for review label Apr 18, 2023
@mlbridge
Copy link

mlbridge bot commented Apr 18, 2023

Webrevs

@openjdk
Copy link

openjdk bot commented Apr 18, 2023

@peter-hofer 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

@naotoj naotoj 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 (with minor nits). Since it would be hard to write a regression test, what kind of tests have you done? Did you run your patch on platforms that made sure your new code path work?

@peter-hofer
Copy link
Author

I have a test in GraalVM which passes with this change in place and will periodically run and start failing in case of a regression. Other issues with this code should become obvious quickly because the code paths are exercised even for non-7bit UTF-8 strings.

@peter-hofer peter-hofer requested a review from naotoj April 19, 2023 07:44
Copy link
Member

@naotoj naotoj 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. Thanks for the change.

@openjdk
Copy link

openjdk bot commented Apr 19, 2023

@peter-hofer 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:

8305746: InitializeEncoding should cache Charset object instead of charset name

Reviewed-by: naoto

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 20 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 (@naotoj) 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
@peter-hofer
Copy link
Author

/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

@peter-hofer
Your change (at version 9d10b1d) is now ready to be sponsored by a Committer.

@naotoj
Copy link
Member

naotoj commented Apr 20, 2023

/sponsor

@openjdk
Copy link

openjdk bot commented Apr 20, 2023

Going to push as commit 20b1d19.
Since your change was applied there have been 25 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

@naotoj @peter-hofer Pushed as commit 20b1d19.

💡 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
core-libs core-libs-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

2 participants