8321489: Update LCMS to 2.16

[alisenchung]

Backport of dc7d3b182d226253ca246dd854c85c4dd964f10e

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8321489 needs maintainer approval

Issue

• JDK-8321489: Update LCMS to 2.16 (Bug - P3 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 32

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk22u/pull/32.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back achung! 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.

[mlbridge]

Webrevs

• 00: Full (8cb189a7)

[prrace]

"Issue of type Backport is not allowed for integrations"

I think this is because you used the backport ID in the PR
You need to use the main bug ID and skara will create / use the backport ID when integrating.

Actually it doesn't look to me like you did this as a backport at all ..

[kevinrushforth]

@alisenchung The problem is that you manually edited the title, when the one Skara suggested is the one you need to use. To fix this, edit the title to use the one Skara suggested:

Backport dc7d3b182d226253ca246dd854c85c4dd964f10e

[openjdk]

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

[openjdk]

⚠️ @alisenchung This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[alisenchung]

/integrate

[alisenchung]

/approval

[openjdk]

@alisenchung This pull request has not yet been marked as ready for integration.

[openjdk]

@alisenchung usage: /approval [<id>] (request|cancel) [<text>]

[GoeLin]

Hi,
thanks for picking this up. It need to be backported to 21, 17 and 11.
Maybe you want to have a look at the instruction in https://wiki.openjdk.org/display/JDKUpdates/How+to+contribute+or+backport+a+fix
We ususally backport these changes to the same release as Oracle does. And as they did not do so yet, it's maybe a bit early for this.

[kevinrushforth]

@GoeLin Alisen works for Oracle and will be doing the backports to the Oracle releases soon. You might look to someone else in the OpenJDK community to pick this up for OpenJDK 21u, 17u, and 11u

[alisenchung]

/approval request upgrading lcms

[openjdk]

@alisenchung
8321489: The approval request has been created successfully.

[GoeLin]

@alisenchung @kevinrushforg ah, you are right, it's 22 not 21 ... but looking at the doc might be helpful anyways.

[openjdk]

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

8321489: Update LCMS to 2.16

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

• dfc86f9: 8321815: Shenandoah: gc state should be synchronized to java threads only once per safepoint
• 251938a: 8324041: ModuleOption.java failed with update release versioning scheme
• 2e91b4e: 8319382: com/sun/jdi/JdwpAllowTest.java shows failures on AIX if prefixLen of mask is larger than 32 in IPv6 case
• af59286: 8324050: Issue store-store barrier after re-materializing objects during deoptimization
• f5dc3ea: 8324280: RISC-V: Incorrect implementation in VM_Version::parse_satp_mode
• 291bd16: 8324659: GHA: Generic jtreg errors are not reported

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

[alisenchung]

/integrate

[openjdk]

@alisenchung
Your change (at version 8cb189a) is now ready to be sponsored by a Committer.

[azuev-java]

/sponsor

[openjdk]

Going to push as commit d0d5064.
Since your change was applied there have been 6 commits pushed to the master branch:

• dfc86f9: 8321815: Shenandoah: gc state should be synchronized to java threads only once per safepoint
• 251938a: 8324041: ModuleOption.java failed with update release versioning scheme
• 2e91b4e: 8319382: com/sun/jdi/JdwpAllowTest.java shows failures on AIX if prefixLen of mask is larger than 32 in IPv6 case
• af59286: 8324050: Issue store-store barrier after re-materializing objects during deoptimization
• f5dc3ea: 8324280: RISC-V: Incorrect implementation in VM_Version::parse_satp_mode
• 291bd16: 8324659: GHA: Generic jtreg errors are not reported

Your commit was automatically rebased without conflicts.

[openjdk]

@azuev-java @alisenchung Pushed as commit d0d5064.

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