8297088: Update LCMS to 2.14

[GoeLin]

I backport this for parity with 17.0.7-oracle.

Omitted patch to Asw2dLibraries.gmk as the warning is already disabled in 17.

---

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-8297088: Update LCMS to 2.14

Reviewers

• Paul Hohensee (@phohensee - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev pull/1030/head:pull/1030
$ git checkout pull/1030

Update a local copy of the PR:
$ git checkout pull/1030
$ git pull https://git.openjdk.org/jdk17u-dev pull/1030/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1030

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1030.diff

[bridgekeeper]

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

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

[mlbridge]

Webrevs

• 02: Full - Incremental (347b4f15)
• 01: Full - Incremental (7d352d25)
• 00: Full (17d5fab8)

[openjdk]

@GoeLin 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.

[phohensee]

Lgtm.

[openjdk]

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

8297088: Update LCMS to 2.14

Reviewed-by: phh

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:

• 339b93b: 8297431: [JVMCI] HotSpotJVMCIRuntime.encodeThrowable should not throw an exception
• b427938: 8297569: URLPermission constructor throws IllegalArgumentException: Invalid characters in hostname after JDK-8294378

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.

[GoeLin]

Thanks for the review!

[GoeLin]

/integrate

[openjdk]

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

• 1dc6a38: 8277822: Remove debug-only heap overrun checks in os::malloc and friends
• c370dec: 8298271: java/security/SignedJar/spi-calendar-provider/TestSPISigned.java failing on Windows
• 339b93b: 8297431: [JVMCI] HotSpotJVMCIRuntime.encodeThrowable should not throw an exception
• b427938: 8297569: URLPermission constructor throws IllegalArgumentException: Invalid characters in hostname after JDK-8294378

Your commit was automatically rebased without conflicts.

[openjdk]

@GoeLin Pushed as commit f2c3f35.

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