8254246: SymbolHashMapEntry wastes space

[coleenp]

The ConstantPool SymbolHashMapEntry is used by class file reconstitution, so the little wasted space doesn't make a difference, but it's fixed here. Tested with tier1 and vmTestbase/nsk/{jdi,jvmti} tests. Should be trivial.

---

Progress

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

Issue

• JDK-8254246: SymbolHashMapEntry wastes space

Reviewers

• Claes Redestad (@cl4es - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk pull/2228/head:pull/2228
$ git checkout pull/2228

[bridgekeeper]

👋 Welcome back coleenp! 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]

@coleenp The following label will be automatically applied to this pull request:

• hotspot

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.

[mlbridge]

Webrevs

• 00: Full (c7df374)

[cl4es]

Looks good and trivial.

[openjdk]

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

8254246: SymbolHashMapEntry wastes space

Reviewed-by: redestad

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 2 new commits pushed to the master branch:

• 982e42b: 8259726: Use of HashSet leads to undefined order in test output
• d6fb9d7: 8255464: Cannot access ModuleTree in a CompilationUnitTree

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.

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

[coleenp]

Thanks Claes!
/integrate

[openjdk]

@coleenp Since your change was applied there have been 2 commits pushed to the master branch:

• 982e42b: 8259726: Use of HashSet leads to undefined order in test output
• d6fb9d7: 8255464: Cannot access ModuleTree in a CompilationUnitTree

Your commit was automatically rebased without conflicts.

Pushed as commit 9ea9323.

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