8321480: ISO 4217 Amendment 176 Update

[luchenlin]

I backport this for parity with 21.0.3-oracle.

---

Progress

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

Issue

• JDK-8321480: ISO 4217 Amendment 176 Update (Bug - P3 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 212

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

[openjdk]

⚠️ @luchenlin 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.

[mlbridge]

Webrevs

• 00: Full (557a3883)

[openjdk]

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

8321480: ISO 4217 Amendment 176 Update

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

• 711ab38: 8322255: Generational ZGC: ZPageSizeMedium should be set before MaxTenuringThreshold
• cc189ff: 8295343: sun/security/pkcs11 tests fail on Linux RHEL 8.6 and newer
• e87638c: 8321122: Shenandoah: Remove ShenandoahLoopOptsAfterExpansion flag
• 90d7b17: 8321120: Shenandoah: Remove ShenandoahElasticTLAB flag
• 7fcfea5: 8324050: Issue store-store barrier after re-materializing objects during deoptimization
• 34d97ab: 8321269: Require platforms to define DEFAULT_CACHE_LINE_SIZE
• 63e52ed: 8318468: compiler/tiered/LevelTransitionTest.java fails with -XX:CompileThreshold=100 -XX:TieredStopAtLevel=1

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.

[luchenlin]

/integrate

[openjdk]

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

• e2cabfe: 8316947: Write a test to check textArea triggers MouseEntered/MouseExited events properly
• 2adc2b4: 8317535: Shenandoah: Remove unused code
• 711ab38: 8322255: Generational ZGC: ZPageSizeMedium should be set before MaxTenuringThreshold
• cc189ff: 8295343: sun/security/pkcs11 tests fail on Linux RHEL 8.6 and newer
• e87638c: 8321122: Shenandoah: Remove ShenandoahLoopOptsAfterExpansion flag
• 90d7b17: 8321120: Shenandoah: Remove ShenandoahElasticTLAB flag
• 7fcfea5: 8324050: Issue store-store barrier after re-materializing objects during deoptimization
• 34d97ab: 8321269: Require platforms to define DEFAULT_CACHE_LINE_SIZE
• 63e52ed: 8318468: compiler/tiered/LevelTransitionTest.java fails with -XX:CompileThreshold=100 -XX:TieredStopAtLevel=1

Your commit was automatically rebased without conflicts.

[openjdk]

@luchenlin Pushed as commit bf7c218.

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